Ray
The most likely cause is a corrupted index. It might have been saved if you
imported it into a blank database (which sometimes fixes bad indices). I'm glad
there was a backup, though. That was good thinking on your friend's side.
Regards,
Bill Mosca,
Founder, MS_Access_Professionals
That'll do IT <http://thatlldoit.com/> http://thatlldoit.com
MS Access MVP
<https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E>
https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E
My Nothing-to-do-with Access blog
<http://wrmosca.wordpress.com> http://wrmosca.wordpress.com
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Ray
Sent: Thursday, April 25, 2013 5:39 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] #deleted in a field value
Can you shed some light on this mystery? A friend has an Access 2003 db and one
table has some rows with #deleted in each field rather than the data that used
to be there. I suspect that they have used the "delete record" button from the
toolbar to delete a few rows (I know, not a good idea) and that something went
wrong. When a query runs on this table it returns an error saying that a record
has been deleted and then stops dead.
We recovered the database from a backup and life has moved on. However, I've
never seen this before, have you?
Many thanks
Ray
[Non-text portions of this message have been removed]
Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (2) |
Tidak ada komentar:
Posting Komentar