View Single Post
  #6  
Old December 15th, 2009, 02:17 AM posted to microsoft.public.access.forms
JamesJ[_5_]
external usenet poster
 
Posts: 32
Default Record Corruption

Thanks for the info.
I also found the following to be useful.

http://www.devx.com/dbzone/Article/42850/1954?pf=true

Thanks,
James

"Arvin Meyer [MVP]" wrote in message
...
Probably. The problem occurs because it is an OLE field. Other OLE fields
and the Hyperlink field are prone as well. What happens is that should
there be a packet interruption during a write, the pointer gets
disconnected from the data. The data is usually still there (not always)
but is inaccessible. That's why some companies can recover corruption.
They carefully look in the file using a hex editor and find the data.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com


"JamesJ" wrote in message
...
Sorry, I meant to ask another question concerning memo fields.

Would I run the same risk of the memo field becoming corrupt (barring
unwanted turning
off of my computer) if the memo field was plain text as opposed to rich
text??

James

"Arvin Meyer [MVP]" wrote in message
...
Memo fields are more prone to corruption because they are not actually
stored in the same table, just a pointer to them. Very often, just the
memo is corrupt, not the entire record. If you go in the table, you can
sometimes delete just the memo field data.

Most corruption is caused by either users inappropriately turning off
their computer or by a bad network card. Corruption can also be cause by
not having a split database if there are multiple users.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

"JamesJ" wrote in message
...
Access 2007 sp2.
I have a rich text memo field in a table with 2 other fields.
Sometimes when I make changes to the memo field I am told that
access can't update the record because it is being "used by another
user"
Not sure of the entire error message but I'll get it because it will
happen again.

From that point on I am unable to make changes the that record. I must
delete the record and create a new one.

Is any one else having this problem?

Must be some limit to something in the rich text memo fields.

James