Give it a try, your application will either lock the database, or allow other applications to access it. Try setting up a DSN and going through it that way.<BR><BR>Best system to use with this implementation tho would be a SQL server, which is made for multiple connections.<BR><BR>-- Whol
You should be on the lookout for these things :<BR><BR>Do not open the database exclusively unless necessary<BR>Create yourself some security system to deal with concurrency issues (entries made by one or another of your client at the same time). IE.: Avoid your Access user to modify what the Web user just did<BR><BR>The way you open your recordsets in ASP can also play a role. Checkout ADO reference guides to learn the different techniques, advantages & drawbacks of each open & lock techniques available.<BR><BR>Eniac
I have experienced the locking out of web users by the someone using Access. <BR>I am looking for the tried and true way. My thoughts is sharing the DB with passwords for everyone who wants to use it web users as well as the MSAccess users. I was trying to avoid implementing security. What do you think.