Undeletable Record in Access 2000

[Guest]

I maintain an Access 2000 database for client case management and I have
approximately 20 users accessing the db.

One of my records is showing #Error for all some fields and ä·¾'s in other
fields. Access will not let me delete or update this record. It is causing a
pop up which says: "Invalid Argument". It also created an autonumer of
1929399923 and when you try to delete the record it gives another warning pop
up of "The search key was not found in any record."

Anyone know how to remove this record?

 

[Ken Snell \(MVP\)]

Sounds like that record is corrupted. Immediately make a backup copy of the
database file, and then you'll need to create a new copy of that table and
copy the "good" data from the corrupted table into the new table.

You may be lucky and be able to just import all the tables with data from
the original file into a new file, but that may not "leave behind" the
corrupted record.

Otherwise, I usually create a new, blank copy of the table and copy the data
into it, leaving out the corrupted record. I then delete the bad table from
the file, rename the new copy of the table to the old table name, and
reestablish relationships, etc. Depending upon which relationships the table
has, and whether it's a parent or child table, this can involve a fair
amount of work.

 

[Guest]

I have also had this problem, I was able to fix it by changing some of the
fields in the table, changed a text field to a memo field, opened the table
closed the table and changed the field back to text and was then able to
delete the record. Don't know why but it worked for me.

 

[Guest]

I can't seem to make a copy, every time I start it stops and says: Invalid
Arguement." Any other suggestions?

Thanks for your help so far!

 

[Ken Snell \(MVP\)]

A copy of ... the table? the data records?

 

[Guest]

Sorry, when I try to copy the table either through export or save as.

 

[aaron.kempf]

MDB is a crappy database engine.

it isn't even a database engine; that's the problem-- MDB doesn't have
a database engine.

Use Access Data Projects against SQL Server or MSDE or something; it is
a much better combination

 

[Ken Snell \(MVP\)]

Did you try creating a new database file and using Import to copy the table
to the new file?

 

[Guest]

Because I have made it a secure db it won't let me access it from a new db...

 

[Ken Snell \(MVP\)]

You'll then need to create a new copy of the table's structure manually.
Then, I usually use the standard "copy/paste" method to get the OK records
(unless you have lots of records), highlighting records in the old table,
using Ctrl+c to copy, then highlight the "new" record in the new table and
using Ctrl+v to paste. Do not try to copy the corrupted record; skip past
it.

(Note: I'm not very knowledgeable about ACCESS security, but I assume that
you can somehow connect to a protected database from another database. Try
searching posts in microsoft.public.access.security newsgroup for info.)