MS access ldb using vb.net

[SBK]

I'm having a problem:

I connect to an MS access db using jet oledb (it has a password). If the db
doesn't have a password, everything works fine. If i do, access gets locked
down (.ldb) with the access db 'Admin' user. Closing the Windows Form that
uses the oledbconnection has no effect on the ldb (even though i close the
connection etc). I can't delete the ldb manually or programatically (after
the .net appication is closed - the ldb disappears). Basically, I want to be
able to compact and repair the database everytime the application is closed.
I'm currently doing this using DAO (which doesn't have access to the db if
it's locked). So, is there a good solution that compacts the db via .net OR
can i somehow shut down the Admin user's use of the access db.

Thanks for any help

[Mary Chipman]

My recommendation would be that if everything works fine without the
database password, then don't use it. The database password feature in
Access is absolutely useless. Anyone who is interested and capable of
doing a google search can bypass it easily. The totally illusory
"protection" it gives isn't worth the hassle. Even user-level Access
security, which is more complex to implement than the databse
password, can be circumvented via google. Basically the bottom line is
if you have sensitive data and/or serious security requirements, don't
use Access.

--Mary

On Tue, 9 Nov 2004 11:24:02 -0800, SBK <SB*@discussions.microsoft.com>
wrote:

I'm having a problem:

I connect to an MS access db using jet oledb (it has a password). If the db
doesn't have a password, everything works fine. If i do, access gets locked
down (.ldb) with the access db 'Admin' user. Closing the Windows Form that
uses the oledbconnection has no effect on the ldb (even though i close the
connection etc). I can't delete the ldb manually or programatically (after
the .net appication is closed - the ldb disappears). Basically, I want to be
able to compact and repair the database everytime the application is closed.
I'm currently doing this using DAO (which doesn't have access to the db if
it's locked). So, is there a good solution that compacts the db via .net OR
can i somehow shut down the Admin user's use of the access db.

Thanks for any help

[SBK]

Thanks Mary

"Mary Chipman" wrote:

My recommendation would be that if everything works fine without the
database password, then don't use it. The database password feature in
Access is absolutely useless. Anyone who is interested and capable of
doing a google search can bypass it easily. The totally illusory
"protection" it gives isn't worth the hassle. Even user-level Access
security, which is more complex to implement than the databse
password, can be circumvented via google. Basically the bottom line is
if you have sensitive data and/or serious security requirements, don't
use Access.

--Mary

On Tue, 9 Nov 2004 11:24:02 -0800, SBK <SB*@discussions.microsoft.com>
wrote:

I'm having a problem:

I connect to an MS access db using jet oledb (it has a password). If the db
doesn't have a password, everything works fine. If i do, access gets locked
down (.ldb) with the access db 'Admin' user. Closing the Windows Form that
uses the oledbconnection has no effect on the ldb (even though i close the
connection etc). I can't delete the ldb manually or programatically (after
the .net appication is closed - the ldb disappears). Basically, I want to be
able to compact and repair the database everytime the application is closed.
I'm currently doing this using DAO (which doesn't have access to the db if
it's locked). So, is there a good solution that compacts the db via .net OR
can i somehow shut down the Admin user's use of the access db.

Thanks for any help