help... corrupt access database... MUST repair

J

Jimmy D

have a 75MB access database. was fine for a log time now when anyone tries
to open it you get: 'Id' is not an index in this table.

obviously something is screwed but i desperately need to open this thing. i
tried compact and repair and it doesnt work... can someone please give me a
suggestion?
 
P

Pat Hartman\(MVP\)

Download the Jet utilities from the MS download site. There is a repair
utility that works a little differently from the compact/repair that you run
from within the database and it frequently can repair an .mdb that the
internal feature cannot fix.

You can also try to create a new empty .mdb and import objects from the
corrupt one. Sometimes that works. When you get to the object that doesn't
work, you bypass it and go back later and recreate it.

And last but not least, get out your backup. You do have a recent backup
don't you?
 
J

Jimmy D

i will try these now

Pat Hartman(MVP) said:
Download the Jet utilities from the MS download site. There is a repair
utility that works a little differently from the compact/repair that you
run from within the database and it frequently can repair an .mdb that the
internal feature cannot fix.

You can also try to create a new empty .mdb and import objects from the
corrupt one. Sometimes that works. When you get to the object that
doesn't work, you bypass it and go back later and recreate it.

And last but not least, get out your backup. You do have a recent backup
don't you?
 
J

John Vinson

have a 75MB access database. was fine for a log time now when anyone tries
to open it you get: 'Id' is not an index in this table.

obviously something is screwed but i desperately need to open this thing. i
tried compact and repair and it doesnt work... can someone please give me a
suggestion?

Just in addition to the other suggestions, check out the resources at
http://www.granite.ab.ca/access/corruptmdbs.htm

John W. Vinson[MVP]
 
A

aaron.kempf

hey you listen to me and listen to me real good

MDB is crap and these sissies don't accept the simple truth that MDB
isn't robust enough to store a single record reliably

USE ACCESS DATA PROJECTS
and SQL SERVER

if you care enough to be building a database in the year 2005; for
christ sakes dont be using MDB

if you care enough to store data in 2005; dont' use MDB.. use SQL

SQL Server or MSDE; i mean-- it's a no brainer

ACCESS DATA PROJECTS rock
 
Top