"red zebra" <info@maldex.be> wrote
[color=blue]
> The last days we had a lot of crasches
> using a application made in Access. there
> appears a screen : this isn't a ms datbase,
> database needs to be repaired. Repairing
> the database can't be done.
> Looking into one of the tables i've seen in
> the ID autonummering under line 40233
> there' a negative number like
> -1232356561313 and under that rule we
> have 5 blanco autonummering rules. After
> these rules the nummering continues 40239
> and the further nummering seems to be OK.
> Deleting those 6 rules can't be done. Does
> anyone know what can be done or where
> i can turn to ?[/color]
This is a symptom of one form of database corruption, and the first thing to
try is to make a copy of the database and run compact and repair -- which
clearly hasn't worked for you.
Next, try creating a new, empty database and importing each object from the
old one -- except the table with the autonumber problem. Write code to copy
the records from that table up to the one just before the first problem
record, then copy records starting just after the last problem record.
Restore the problem records manually. Don't worry that their autonumber
fields aren't in sequence -- that is not their purpose.
Make certain you have all the Service Packs and patches for both Access and
the database engine installed. Make certain you do not have multiple users
logged in to the same front end or monolithic database (because that
significantly increases the probability of corruption).
If you just can't salvage it, contact Peter Miller at
http://www.pksolutions.com. He has an outstanding reputation for data
recovery and, unless he has changed his policies, will tell you in advance
how much it will cost you.
Larry Linson
Microsoft Access MVP
