Curious Question Re: db1.mdb

[CassandraB]

I've got a curious question...periodically I'll look at the workspace that houses the Access application that I created that users use... at times there will be an additional file 'db1.mdb' in there (and it is always called db1.mdb). Why is it created? And would it be wrong to just delete it? Because that is what I've been doing. Please someone advise, thank you.

 

[Mile-O]

You mean: db1.ldb???

It's the record locking information. Don't delete it.

 

[Mile-O]

Q136128

 

[AnotherWayne]

Cassandra,

No, don't delete it!

If you do a repair/compact, and it fails, this is most likely your
"best" copy of the database. There is something in your
database that does not let the compact/repair run to its
completion. That should be fixed, before you can truly
compact/repair.

In the meantime, don't delete that file.

Another Wayne

 

[CassandraB]

The file is not an .ldb file, it's an (db1).mdb file. Since we're on the subject, today I came across a file that was named the same as the database but it had a '_backup' attached to the end of it. Why was that created?

What kind of damage did I do to the database by deleting them - because I have been doing it all along, because I didn't know! I synched 4 replicas today and it seemed to work. What can I expect?!

 

[CassandraB]

Wayne, how can I figure out what to fix when I don't know what is wrong. I'm at my wits end with this whole project. Thanks.

 

[AnotherWayne]

Cassandra,

There is something "wrong" within your database. When
Access does a Compact/Repair it opens a new database
(db1.mdb) and one-by-one it copies the items in your
database to the new one. When it finishes, it deletes
your current database and renames the db1.mdb to
your database name.

In your case, in processing an item: a form, query, table, or module it comes accross something it doesn't understand.
It will, sometimes, include that object in the new database.
The bottom line is that Access is "happy" with your "new"
database. It is very close, or exactly like your original
database.

Some people, just accept this and go on with life. But if
you want to, there are some things that you can do. First,
you can compile your entire DB and when successful retry
the Compact/Repair. If is still not OK, you can make a new
blank database, import all of the elements from your
original database. Then you should be OK.

There are times when a form goes "brain dead" and has
to be rewritten. These just illustrate the importance of
backing up your DBs often and even copying things like
code out to external documents for safekeeping.

There is no "easy" way to pinpoint what is wrong with
your DB, but in investigating its parts, you will learn
quite a bit about it.

Good Luck,
AnotherWayne

 

[gemma-the-husky]

if you create a new database, by default it will be called db1, db2 etc. I suspect you have created one and forgotten about it.

you should be able to open it, and see whats in it - the windows date will indicate when you created it.

if its an caused by an error condition, as wayne says, you should be aware of this

 

[motleyjew]

I'm not sure if this is the same situation, but when I first started with my department the users were sharing a database without it being split. In these cases it would create a file similar to what you are talking about. I'm pretty sure it was db1, then db2 sometimes. I tried to recreate it the scenario, but I couldn't do it. Maybe the same thing is going on with yours?

Gregg

 

[shadow9449]

I want to point out that you should never compact a shared file over a network if there are other people in it.

Standard practice in sharing Access databases is to split the front end and back end and give each user their own front end. Often, especially with a small number of uses people deploy access databases by simply putting it on a shared drive and having everyone shortcut into it.

If you've done the latter, you should never have a user try to compact while people are using the file or you will get that db1.mdb situation you describe.

SHADOW