View Single Post
  #19  
Old December 18th, 2009, 11:25 AM posted to microsoft.public.access.forms
JamesJ[_5_]
external usenet poster
 
Posts: 32
Default Record Corruption

In my case none of the things you mentioned occurred.
There is a possibility that power might have been interrupted
and the computer shut down but I can't recall that happening.
In that case wouldn't all my memo fields become corrupt?
I'm not on a network and don't share the db with anyone and
I have no settings allowing my computer to sleep.
I to never had problems with memo field corruptions when I
ran my db with access 2003. Only since I've been uising ac 2007
has this problem poped up.

Have you converted your db to 2007 format, ran it for a while
and see if the memo fields become corrupted?

James

"Arvin Meyer [MVP]" wrote in message
...

"JamesJ" wrote in message
...
This is only to segregate the memo field from the rest of the record?
Even now I find that when the memo field gets corrupted I can
go to the table and delete the text from the memo field and the
the record is ok. I just need then to put the data back into the memo
field.

If that's the case, even replacing the record wouldn't be much more work
than replacing the data in the memo field.
It seems that the corruption of the memo field occurs when there is a
large amount of data in it.


The corruption is not data centered. Practically all corruption occurs
because there is a loss of connectivity. Either a machine is turned off
without backing out, or packets are dropped due to a bad network card, or
even a hard drive is asleep when you are trying to write to it.

I have an Access 97 database with more than 6 thousand records in a memo
field. I'd guess the average record is about 2 to 3 K. The largest records
are more than 64 K. It was converted from an Access 2.0 database, 10 years
ago, and has never corrupted in either version, so size is definitely not
the cause.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com