Mark,
Thank you very much for your response.
The problem seems to happen when I open *any* of my tables. I've also
found
that Access crashes on me when I try changing the design of a saved query
[in
the problematic database]. Unfortunately, this is a database of nearly a
gigabyte, and has millions of records in some of the tables. Mind if I
ask a
few more questions...
1. Did you happen to know what records you should find in your query?
I'm
trying to figure out what to compare it against.
2. Do you think it would help for me to simply create a new database and
im****t the tables?
3. Or, perhaps, I could create a new database, im****t just the structures
of
the tables, and then use "linked tables" and "append queries" to populate
the
new tables? (Then I could populate those tables overnight using a macro,
and
I'd keep my indexes. And using queries might exclude any corrupt
records.)
Grateful for any suggestions,
Benjamin / nimajneB
Mark wrote:
>I've had this problem in the past and found it to be a corrupt record in
a
>memo field. Luckily, there were not too many records and identified it
from
>the query results. I then used the primary key from the query results to
>create a delete query to remove the corrupt record.
>
>Hope this helps,
>
>Mark
>
>> Can anyone offer me any insight on the following problem?
>>
>[quoted text clipped - 6 lines]
>> Even though my data seems fine *for now*, it's a little scary for me.
>> Insight? Possible solutions?
--
Message posted via http://www.accessmonster.com
|
