G
Guest
I have a database (Access 2000). I access it via a webpage (asp) to present
a report page. Multiple people can open the database directly, but when
trying to run the asp file via the web, only one user can get the correct
page. Everyone else receives:
A problem was encountered while connecting to name.mdb
Error source: MicroSoft JET Database Engine
Error description: Could not use";file already in use
Error Number: -2147467259
I cannot tell if it is how I am trying to connect to the database or how the
database is structured. I inherited this project from someone I can no
longer contact.
We have a button on the page that opens a separate window and actually opens
the database. The default mode for the database is "Shared", so several
people should be able to open it at once. Are you saying that if someone
opens the database, the asp page won't be able to access it?
The database is located on the server with the web files. This worked on
a different network, but when they moved to this one we started having all
these problems. The page provided an option to actually edit the database
and we had no problems before. When the database is accessed via the asp
code, is it supposed to "lock" the database? It seems to me it was
supposed to open the page, present the report (sorted however the user
wants), then release the database for the next person. Does this sound right?
Any help would be greatly appreciated.
Thank you
a report page. Multiple people can open the database directly, but when
trying to run the asp file via the web, only one user can get the correct
page. Everyone else receives:
A problem was encountered while connecting to name.mdb
Error source: MicroSoft JET Database Engine
Error description: Could not use";file already in use
Error Number: -2147467259
I cannot tell if it is how I am trying to connect to the database or how the
database is structured. I inherited this project from someone I can no
longer contact.
We have a button on the page that opens a separate window and actually opens
the database. The default mode for the database is "Shared", so several
people should be able to open it at once. Are you saying that if someone
opens the database, the asp page won't be able to access it?
The database is located on the server with the web files. This worked on
a different network, but when they moved to this one we started having all
these problems. The page provided an option to actually edit the database
and we had no problems before. When the database is accessed via the asp
code, is it supposed to "lock" the database? It seems to me it was
supposed to open the page, present the report (sorted however the user
wants), then release the database for the next person. Does this sound right?
Any help would be greatly appreciated.
Thank you