All I am looking for a good documentat regarding limitations of access.
Access is pretty good when an application is written correctly. However, it
does not include the ability to create transaction logs to roll back
operations, if required. If the information is mission critical (ie. the
company would be hurt if they suffered any downtime due to a corrupted JET
database), then SQL Server should definitely be considered. Here is a recent
thread that you might want to read:
http://groups.google.com/group/micr...read/8af2400c47b4bfa5/61c3d6b6aea36648?lnk=st
It starts out with an answer by MVP John W. Vinson. To see the original
question--and I'm not sure why one needs to do this--click on "Show quoted
text".
If you do end up converting an Access app. to use SQL Server, then I highly
recommend obtaining a copy of the book titled "Microsoft Access Developer's
Guide to SQL Server", written by Mary Chipman and Andy Baron (SAMS
Publishing). Here is a link to the book at Amazon.com:
http://www.amazon.com/exec/obidos/t...103-5399559-8631817?v=glance&s=books&n=507846
Early in the book (page 6) the authors write:
"Many people think that upsizing from the Jet database engine to SQL Server
is a universal panacea for whatever is ailing their Access databases. It's
not. In fact, just the opposite is usually true. If your Access application
is a dog, then most likely it will still be a dog after you upsize it to SQL
Server--perhaps an even bigger, uglier, shaggier dog! Even a well-designed
Jet database often won't run any faster after the tables are upsized to SQL
Server if you are using the same data access methods you used for your Access
database. In order to successfully convert your Access database, you have to
be clear about why it needs to be upsized, and you need to understand how to
take advantage of the strengths of SQL Server by reworking the data access
elements of your Access application."
I hope this helps some...
Tom
http://www.access.qbuilt.com/html/expert_contributors.html