ASP/Access 2000 problem

[Brent]

I've got a site that uses ASP pages to make simple
connections to an Access 2000 database. The site has been
fine for the past few months. Last night I browsed to an
ASP page, and for some reason an .ldb file got created on
the server, and now none of the pages can connect to the
database. I've tried a compact/repair on the db, I've
even created a new database and imported all the files
into it, but that one did the same thing. Any ideas on
why this is happening or how to fix it? Thanks.

 

[Brent]

Okie dokie.. This is an interesting one.. There is a
fairly simple query (has about 2 joins in it, otherwise
very simple) I had created that bombs out Access. I tried
running this on my desktop and it gave me an "Access has
encountered an error and must be shut down" error. Never
seen that before...

 

[Phillip Windell]

An LDB file is a temporary file that is created when "something" has
the MDB file open. When the MDB file is closed the LDB file
disappears.

For example:
If you open the file in Access, an LDB file is created. At this point
there are no adverse effects. But if you open one of the Tables from
within Access then none of the Web pages that need that Table will
work until you close the Table. You may continue to keep the MDB file
open in Access, that by itself won't cause a problem.

If you apply this concept to your situation you may find the source of
the problem.

--

Phillip Windell [CCNA, MVP, MCP]
(e-mail address removed)
WAND-TV (ABC Affiliate)
www.wandtv.com

 

[Bob Barrows]

An LDB file is a temporary file that is created when "something" has
the MDB file open. When the MDB file is closed the LDB file
disappears.

Minor correction:
The first user that opens the database (non-exclusively) needs to be able to
create the ldb file. Subsequent users need to be able to write to the ldb
file to add their names to the list of current users in the file. As each
user closes the database, he needs to be able to remove his name from the
list of current users in the ldb file. The last person who closes the
database, even if it's not the person who originally opened the database and
created the ldb file, needs to be able to delete the ldb file. This is why
all database users (including IUSR_machine) need read/write authority to the
folder containing the mdb file, if you need the database to support
multi-user activity.

If the ldb file cannot be created, then the database is opened exclusively,
and sometimes, read-only.

For example:
If you open the file in Access, an LDB file is created. At this point
there are no adverse effects. But if you open one of the Tables from
within Access then none of the Web pages that need that Table will
work until you close the Table.

?
That hasn't been my experience. As long as IUSR has read/write authority to
the folder containing the mdb file, it should be able to access any table in
the database unless a lock is present. Having the table open in a datasheet
in Access does not lock the table ...

Just in case, I just tried it. As expected, the asp page had no problems
writing to a table that I had open in Access.

Bob Barrows

 

[Phillip Windell]

That hasn't been my experience. As long as IUSR has read/write authority to
the folder containing the mdb file, it should be able to access any table in
the database unless a lock is present. Having the table open in a datasheet
in Access does not lock the table ...

(Aside from my typos, ..sorry) What I have had happen is the MDB file
was directly opened using Access on the server. It opens under the
authority of the currently locally logged on user (not IUSR). While it
is open I open a browser on another machine and go to the site. As
long as I didn't actually open a table in Access all was well, but if
I opened a Table the Site couldn't do anything with the database
involving the same Table until I closed the Table in Access.

--

Phillip Windell [CCNA, MVP, MCP]
(e-mail address removed)
WAND-TV (ABC Affiliate)
www.wandtv.com

 

[Bob Barrows]

(Aside from my typos, ..sorry) What I have had happen is the MDB file
was directly opened using Access on the server. It opens under the
authority of the currently locally logged on user (not IUSR). While it
is open I open a browser on another machine and go to the site. As
long as I didn't actually open a table in Access all was well, but if
I opened a Table the Site couldn't do anything with the database
involving the same Table until I closed the Table in Access.

That was exactly the scenario I tested. The asp page had no problem updating
the table I had open in Access. I used an Update statement - I did not try
opening a recordset.

Bob Barrows

 

[Phillip Windell]

That was exactly the scenario I tested. The asp page had no problem updating
the table I had open in Access. I used an Update statement - I did not try
opening a recordset.

Ok,..well maybe it was the type of cursor I used?...dunno. But
anyway,...I think we answered his question about what was the LDB file
all about

--

Phillip Windell [CCNA, MVP, MCP]
(e-mail address removed)
WAND-TV (ABC Affiliate)
www.wandtv.com