rows with #delete in them. I've had data vanish before
but it's always been an application. I've been over the
code and looked at all the deletes and update be none of
them could drop the rows.
Hmm. I have not once, not ever heard of Access simply dropping rows,
though memo fields have been known to go missing due to corruption. I'm
trying to think whether index corruption could cause rows to go missing
without a trace, but I don't think so. Try running a SELECT COUNT query
on some field in the table that is not indexed; e.g.,
SELECT COUNT(SomeUnindexedField) AS NRecs
FROM MyTable;
and see if that count differs from the count you get when you simply
open the table in datasheet view. I don't know if this would turn up a
discrepancy even if the primary index is corrupt, but I figure it might.
If this is a very big table, how do you know that there are rows
missing? Is it a discrepancy in the total number of rows, or are you
looking for specific values that should be found but aren't, or what?
How many rows do you believe are missing, and do they have anything in
common?
At this point, my money would be on either code or queries that delete
or update records that they shouldn't, or else a user who is manually
deleting records. I've seen it happen, for example, where a user has
made a copy of a form and then deleted all the records out of it,
thinking "it's only a copy of the original form, so I can delete from it
wthout affecting the original form and its records."
