Lock remains (.ldb) after finishing with Access in Excel

[GBall]

Hi,
I've modified a spreadsheet to populate a range with data from an Access database using vba.
After populating the range, I close the recordset and database and set them both to nothing - they are not accessed again.
However, when I close the spreadsheet, the lock file remains.

TIA
Graham

 

[Databaseguy]

You need delete permissions in the directory where the database resides. Tyrone Lumley
augerinn@gte.net

http://server47.hypermart.net/databaseguy

 

[GBall]

but, I can delete the file myself via explorer.

 

[Databaseguy]

Hmmmmm....

Drop the ldb file in notepad. Who does it say is in the database ?? Tyrone Lumley
augerinn@gte.net

http://server47.hypermart.net/databaseguy

 

[GBall]

Admin, by the look of it.

ISD-01322  …åøw¨Û  Admin pLöwH šMöw

 

[Databaseguy]

Then you've secured the DB using the Wizard, right ?? Tyrone Lumley
augerinn@gte.net

http://server47.hypermart.net/databaseguy

 

[GBall]

Not as far as I'm aware. I've come cold into this and just got sent the db from the user. I can open it with no problem at all. We're running Nt, but I don't think that should be a problem.

 

[Databaseguy]

That's strange. I just instanciated a DB on my desktop using Excel. I set a break at the opendatabase method. At that point, there was an LDB on my desktop. Once I went past that line of code, LDB went bye.Hmmm.

Have you downloaded Jetutil.EXE from MS ??? It'll tell you who's in the LDB. Thoses characters just don't look right. For example, my LDB just says

LUMLEYT admin

Now that I read your original post, is your machine name or login ISD-01322 ???

I'm currently figting orphaned LDBs and File Locks myself in a multi user enviroment. If I run across something concrete, I'll let you know. This much I know now:

1. If you don't have delete rights where the database resides, the LDB will remain after you exit the database. I'm unsure what happens next. I think if someome else can get in, and they have rights, the LDB is destroyed.

2. If you open a database where there are no users logged in, and you only have read rights to the directory, you'll lock everyone else out until you exit. Even if the DB is set to Shared.

3. If you have a front end-back end DB, no LDB is created on the back end. Only the front end.

4. Sometimes something gets a hold of the process. Server/thread/whatever (I'm not sure) and won't let go. The only workaround I've seen is to re-boot the server. (Ouch)

5. Access defaults to the last open method used when you use a shortcut or recent file menu. To get around this, open access first, then use the file/open method.

Tyrone Lumley
augerinn@gte.net

http://server47.hypermart.net/databaseguy

 

[GBall]

Yes, ISD-01322 is the computer name I'm using.
I've also tried running it on my C: drive (it was previously in my shared networks folders), with no difference at all.
I did notice that the ldb was created wherever the db was located, which seems to gainsay what you pointed out in item 3.
Looks like it will remain one of life's little mysteries B-)