G
Guest
I have a front end database application in MS Access 2000, which for purposes of discussion has an administrative part and a user part. I recently decided to experiment with trying to move the user part of the front-end, which services about 70 people to a .net application. I've implemented both a form and web version. My intent for the time being is to leave the administrative part which is more involved in MS Access which is used by only a couple of people.
The problem I'm running into is that multiple instances of each application (.net or MS Access) can access the backend database using individual connections as long as only that application is used, however if either application tries to open the backend database while the other application has an open connection it will complain about the backend being locked (or file already in use).
Does anybody understand why the files would only be locked files when accessed by different applications? Have I encountered a limitation with MS Access or is there a setting or work around that would allow me to use both front-end applications simultaneously?
Thanks for any input
Steven W
The problem I'm running into is that multiple instances of each application (.net or MS Access) can access the backend database using individual connections as long as only that application is used, however if either application tries to open the backend database while the other application has an open connection it will complain about the backend being locked (or file already in use).
Does anybody understand why the files would only be locked files when accessed by different applications? Have I encountered a limitation with MS Access or is there a setting or work around that would allow me to use both front-end applications simultaneously?
Thanks for any input
Steven W