Issues converting to SQL Server

B

Bill Sturdevant

I have several Access databases that use replication/synchronization to make
them "multi-user". Users do their thing during the day, then send their DBs
in for night-time synchronization and get a fresh copy via email in the
morning. I did it that way because we could not get access to a central
server.

It has been somewhat successful, but is prone to difficulties and logistical
issues. The biggest thing is lack of ability to connect real time to a
central database.

Now I have access to a central server with MS SQL Server installed, and I
want to convert my Access databases to SQL Server databases. I have
successfully converted the tables and data.

But, how should I convert the applications? Should I leave them as MDB
front ends, but convert the record sources to stored queries? Should I
convert them to ADP front ends? I am just digging into this and do not want
to get too far down one road and find out the other was better.
 
T

Tony Toews

Bill Sturdevant said:
But, how should I convert the applications? Should I leave them as MDB
front ends, but convert the record sources to stored queries? Should I
convert them to ADP front ends? I am just digging into this and do not want
to get too far down one road and find out the other was better.
Click to expand...

I agree with Arvin. ADPs are likely more work than required. And
they may be at a dead end evolutionary wise.

Do a search at the Knowledge Base at support.microsoft.com using the
keywords "upsizing" to review the various white papers on upsizing
Access to SQL Server as well as to ensure you have any updates
required.

Also see my Random Thoughts on SQL Server Upsizing from Microsoft
Access Tips page at
http://www.granite.ab.ca/access/sqlserverupsizing.htm

Tony

--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Top