The .ldb file is created when the database is being accessed. If you've
graphically made your connection to Access (using the Server Explorer
window), then even though your code is done using the db, VS.NET continues
to use it. Also, ADO.NET uses connection pooling, so even when you close
your connection and it falls out of scope, it still exists in the connection
pool. If you add: OLEDB Services=-4 to your connection string, you can
indicate that you don't want to use connection pooling.
"Joe" <Jo*@discussions.microsoft.com> wrote in message
news:0C**********************************@microsof t.com...
Hi,
I am using MS Access DB in the backend of an ASP.NET login page. The DB is
small and has only two tables. I have noticed that besides using close()
on
OleDBDataReader and OleDbConnection object, this database gets locked
(.ldb
file). Religiously I use close() after I am done with the existing
connection. I was wondering if there is any way to prevent it from locking
up.
Thanks,
Joe