.ldb file converts to mdb file

[Cordman]

I did a search of the forum and didn't really come up with a solution, so...

When I open my database, which is on our company server, it creates the lock file (.ldb). When I exit the db, access "converts" the .ldb to a full database with the .mdb extension. This just started happening when I got a new computer system (win xp & Office 2003). If I copy the db to my HD and open it, it creates the .ldb and when I exit, the lock file disappears as expected.

My prior system worked as expected whether on the server or HD. Any ideas/suggestions? TIA

 

[pbaldy]

I hesitate to say anything is impossible, but this sounds impossible. Is the new file db1.mdb? If so, that's probably a result of a failed compact on close.

 

[Cordman]

Is the new file db1.mdb? If so, that's probably a result of a failed compact on close.

Exactly. If I leave the db1.mdb in the folder and re-open the original db, when I exit that, I'll have db2.mdb, db3.mdb, etc., etc. I do have the db set to compact on close, so my question now is... is there any way to prevent this "failed" compact on close? Thanks!

 

[pbaldy]

I can't find a link right off, but there's a school of thought that says you shouldn't compact a db over the network. You seem to be validating that, as you don't experience the problem when the db is local, only when it's over the network. I'll try and find a helpful link.

 

[pbaldy]

This FAQ on another site addresses the issue, in the last section:

http://www.utteraccess.com/forums/s...1561733&page=0&view=collapsed&sb=5&o=&fpart=1

 

[Cordman]

This FAQ on another site addresses the issue, in the last section:

http://www.utteraccess.com/forums/s...1561733&page=0&view=collapsed&sb=5&o=&fpart=1

Thanks pbaldy. The only thing that I find confusing is when I had my other machine the other day, this was not an issue. Only with this new one, but I'll do the compacts as they suggest in that article. Thanks again!