G
Guest
Hi Brent,
It is never a good idea to share an entire Access application. Microsoft
personnel on the Access team have previously identified sharing an entire
database as the number one cause of JET database corruption. The application
should be split into two .mdb files: a front-end (FE) and back-end (BE) file.
A copy of the FE file should be placed on each users local hard drive. The BE
file, which contains the tables with the shared data, is placed on the file
server. With this type of arrangement, there is no need to involve a web
browser.
Implementing a Successful Multiuser Access/JET Application
http://www.access.qbuilt.com/html/multiuser_applications.html
Tom Wickerath
Microsoft Access MVP
http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
It is never a good idea to share an entire Access application. Microsoft
personnel on the Access team have previously identified sharing an entire
database as the number one cause of JET database corruption. The application
should be split into two .mdb files: a front-end (FE) and back-end (BE) file.
A copy of the FE file should be placed on each users local hard drive. The BE
file, which contains the tables with the shared data, is placed on the file
server. With this type of arrangement, there is no need to involve a web
browser.
Implementing a Successful Multiuser Access/JET Application
http://www.access.qbuilt.com/html/multiuser_applications.html
Tom Wickerath
Microsoft Access MVP
http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________