Here's my dilemma:



I have a  web site using ASP as a front end into an ACCESS database.

Everything works fine. However I have a group users who need to be able

to manually open the Access database. Whenever they do open the database

manually I get ODBC errors saying that the file is already open. Is

there a way around this problem? Why is it that multiple users can open

an access database and write to it, but an error occurs for the ODBC

connection if a user has the database open?

This would probably be the same problem with almost any scripting language

and Microsoft Access:-

Access has a violent hatred of having its tables openned in the actual

Access application at the same time as a script tries to write/read to/from

it. The reason, i believe, is because the DB locks itself as it is being

read/wrutteb and since a normal script command opens and closes the DB so

quickly its designed to handle multiple, split-second, queries. Where as

openning the DB tables themselves are like some ridiculously long session!



I don't know a solution, however i'd recommend you allow this user group to

do modifications to the DB by using some 3rd party ASP database

administrator application. Similar to phpmyadmin for MySQL. Because its just

yet another script, they are unlikely to run into the problems you are

having currently.





--------------------------

Dave Cranwell

Torchbox Ltd

david@t...

tel: (+44) 1608 811 870

mob: (+44) 7760 438 708

http://www.torchbox.com



----- Original Message -----

From: "jlane" <jlane@t...>

To: "ASPToday Discuss" <asptoday_discuss@p...>

Sent: Friday, December 14, 2001 1:21 PM

Subject: [asptoday_discuss] ASP and MS ACCESS





> Here's my dilemma:

>

> I have a  web site using ASP as a front end into an ACCESS database.

> Everything works fine. However I have a group users who need to be able

> to manually open the Access database. Whenever they do open the database

> manually I get ODBC errors saying that the file is already open. Is

> there a way around this problem? Why is it that multiple users can open

> an access database and write to it, but an error occurs for the ODBC

> connection if a user has the database open?

>

>

>

>

>