Re: Converting to SQL Server
- From: "Powderfinger" <PFinger@xxxxxxx>
- Date: Wed, 9 Jan 2008 09:04:19 -0500
It seemed to work incredibly well. even without touching the VBA code, which
I had made sure was ADO. I did not have to create any stored procedures or
views. I'm almost in shock. The macros work , which I did not think was
going to based upon some articles i read.
The db is relatively simple and small, a fews forms and reports centered
around a contact table which has about 500,000 records in it. Right now I
have the trial db on a windows 2000 machine running SQL server 2005 trial
version, and a single client with Access 2003. What astounds me the most is
that I did not have to make any modifications to the client. Just share a
directory on the server and plop the file down, just like you would do for a
normal access file. I guess it automatically figures out the ODBC
connection.
I did order the book that Dale suggested. I know that there are several
different ways to hook up an access front end with a server db. My biggest
question mark is, if i go to production , what happens if the db goes
corrupt? I have a lot to learn.
"Klatuu" <Klatuu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0C4DB072-C339-4054-AD80-D119DBF6602E@xxxxxxxxxxxxxxxx
Use the upsizing wizard.anyone
Tools, Database Utilities, Upsizing wizard.
--
Dave Hargis, Microsoft Access MVP
"Powderfinger" wrote:
I'd like to convert a database from Access 2000 to SQL server. Does
have any advice as to how to get started?
.
- Follow-Ups:
- Re: Converting to SQL Server
- From: JohnE
- Re: Converting to SQL Server
- References:
- Converting to SQL Server
- From: Powderfinger
- Converting to SQL Server
- Prev by Date: Re: Prompt user for filename
- Next by Date: Checkbox with calender control
- Previous by thread: Converting to SQL Server
- Next by thread: Re: Converting to SQL Server
- Index(es):
Relevant Pages
|