Getting "repair database" message when opening

[Randee]

I'm getting this msg:
The database (and it lists the location of the file) needs to be repaired or
isn't a Mircosoft Access database file. You may have quite MS Access
unexpectedly with the database open....." and then it tell you to repair it
by using the DB utilities under the Tools menu. I click that and get a
window that shows unrelated files and it says at the top of the window
"Database to Compact From". I have no idea what that means. I cannot
simply delete this file, or move it either (like putting it in a folder and
out of my way). Any help would be great.
Thanks,
Rande

 

[aaron.kempf]

I'd really really reccomend not using MDB for anything; you must have
missed that memo.

MDB isn't reliable enough for real-world use; and it hasn't been for
the past decade.

-Aaron

 

[John Vinson]

I'm getting this msg:
The database (and it lists the location of the file) needs to be repaired or
isn't a Mircosoft Access database file. You may have quite MS Access
unexpectedly with the database open....." and then it tell you to repair it
by using the DB utilities under the Tools menu. I click that and get a
window that shows unrelated files and it says at the top of the window
"Database to Compact From". I have no idea what that means. I cannot
simply delete this file, or move it either (like putting it in a folder and
out of my way). Any help would be great.
Thanks,
Rande

You might be trying to open a database that was created with a more
recent version of Access than the version you have installed; e.g.
Access 97 cannot open an Access 2000 database. Or the database might
indeed have been corrupted.

The "Compact" option - when you don't have a database open - prompts
you for the "database to compact from". Read this as "the database
that needs to be repaired" and navigate to your .mdb file and see if
it can repair the problem.

See http://www.granite.ab.ca/access/corruptmdbs.htm for a good
discussion of database corruption, its prevention and cure... but be
aware that some forms of corruption can irrevokably destroy the
database.

John W. Vinson[MVP]

 

[aaron.kempf]

or of course, you could just be trying to use an UNRELIABLE database.

these dipshits around here will blame it on the network; and they'll
blame it on the harddrives.. and they'll blame it on EVERYTHING

the root of the problem is that MDB isn't reliable.

move to SQL Server, Oracle, mySql or DB2; no exceptions

-aaron