I use asp pages in which in each, 2

[avivit]

I use asp pages in which in each, 2 different databases are accessed there. The main database is a read only, and the other has write permissions. Anyway, in these asp pages there is only retrieval of data. NOT any kind of "write".
These pages are located on the INTRANET.
(The database with the write permission, is updated through
totally another pages, and are updated once a in life time by me and another staff member only. No "write" is being done theses days, and I still get the error).

The error I get once a day, wheh accesing the asp pages is is:

"Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access 97 Driver] Couldn't use '(unknown)'; file already in use."

I checked microsoft and there is an explanation in the following link:

http://support.microsoft.com/support/kb/articles/Q174/9/43.ASP

I have no idea what it syas, and would like to understand the meaning of it in simple english.
What kind of permission is missing for the page to be seen properly?

 

[avivit]

Forgot to mention: I use MS-ACCESS, and the problematic line in the asp pages is the one that holds the DSN of the database wuth the write permission.

Thanks

 

[Bixarrio]

I get that error when I access a db of which I just opened the table in access. If I close the table (or better even, access), the error disappears. Make sure you close access on the server. _________________
Bixarrio
e = m * (c ^ 2)

 

[wushutwist]

Also make sure you don't use Access. Sorry couldn't resist. Wushutwist

 

[avivit]

Bixarrio, U mean u closed the connection but not the recordset and had this error?

If I set rs but do not open it, shall I cancel it (set rs=nothing)? Is it necessary? required?

I just check all pages, and all reordsets and connections are closed at the end (and it always reache the end).

Is there a way to response.write the status of a database? table? recordset?

 

[NightWatcher]

In case you need an answer fast, I think what Bixarrio meant, was, that, he gets the error when he has ACCESS (the application) opened (with the db on it).. But when he closes the application (Access) the error disappers when the DB is accessed through ASP..

Did I make myself clear? It's a bit awkward to explain it, when you have ACCESS the application, and ACCESS as in the means to access something. Sorry if it does not go trought, I done my best..

Hope it helps.


NightWatcher

 

[avivit]

Got it. Well, We do not open the ACCESS db, but only through asp, and the last time it was updated was long time ago.
The other asp pages only access it to read from, but seems all recordsets, and connections are closed and set to Nothing. And I still get this error msg once a day.

 

[avivit]

Thanks all for helping out.
It looks ok now, since I changed sonething there:
In one of the asp pages, I set a recordset, and actually really opened it, only if a certain condition happened. Did not use it if no condition, and did not set it to nothing.
Now it is fixed (looks like it), by setting the rs, only if a certain condition happen. There I open it, and eventually close it and set to nothing.I do not open a recordset if a condition does not happen.

Thankssssssss very very much...