Quote:
|
Originally Posted by rickp
At a very high level, when you upsize Access to SQL (it's a native feature of Access) Access will create the tables and data in SQL for you. Once that is finished, you create linked tables to the SQL database and rename the linked tables what your local tables are. This means you use the same Access database you have now and your forms, queries, reports VBA all think it's using the same data. No, recoding not even user training because to them, it's the same thing but on the back-end the data is in SQL.
A few advantages are:
1. Access does not handle multi-users access that well
2. SQL will defintely have better performance and backup capabilities.
3. No need to compact the DB anymore.
If your access file is corrupt now especially with all that data, you could be up the creek without a paddle. I'm sure you can restore from backup but what if somone spent all morning entering data?
Once you get to SQL, you can do some more uber cool things in the future like making it web based or at least some part of it web accessible like reports.
My $.02
More info -> http://www.aspfaq.com/show.asp?id=2182 |
Thanks for the info. It looks like something to look into after we upgrade the computers.
I have noticed a couple of problems with multiple users on access:
1) If someone's computer locks up while they are in Access, upon rebooting and trying to get back in, it tells them the database is corrupt and that the system has to repair it. In order to repair, all other users must exit the database. This is not a big deal as we usually only have 2 or 3 users, but is indeed an inconvenience at times.
2) If 2 users are editing data in records that are chronologically near eachother in a table, one user will lock the records that the other user is trying to edit. So user #2 must wait until user #1 is finished. Again, this does not happen that often.
Those are the only 2 complaints that I have had.