A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Using Forms
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Record Corruption



 
 
Thread Tools Display Modes
  #1  
Old December 14th, 2009, 08:43 PM posted to microsoft.public.access.forms
JamesJ[_5_]
external usenet poster
 
Posts: 32
Default Record Corruption

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

  #2  
Old December 14th, 2009, 09:44 PM posted to microsoft.public.access.forms
Arvin Meyer [MVP][_2_]
external usenet poster
 
Posts: 2,310
Default Record Corruption

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



  #3  
Old December 14th, 2009, 10:48 PM posted to microsoft.public.access.forms
JamesJ[_5_]
external usenet poster
 
Posts: 32
Default Record Corruption

No multiple users and the db is split.
Maybe a short loss of power might have shut my computer off but I'm not
sure.

Next time it occurs I'll delete the memo field data at the table level and
see if that
will, at least, allow me to keep the record.

Thanks,
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



  #4  
Old December 14th, 2009, 11:08 PM posted to microsoft.public.access.forms
JamesJ[_5_]
external usenet poster
 
Posts: 32
Default Record Corruption

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



  #5  
Old December 15th, 2009, 02:23 AM posted to microsoft.public.access.forms
Arvin Meyer [MVP][_2_]
external usenet poster
 
Posts: 2,310
Default Record Corruption

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





  #6  
Old December 15th, 2009, 03: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





  #7  
Old December 15th, 2009, 03:39 AM posted to microsoft.public.access.forms
Linq Adams via AccessMonster.com
external usenet poster
 
Posts: 1,474
Default Record Corruption

To add to the mix, RTF, in v2007, is actually stored as stores HTML, which
may, in fact, add to the chance of corruption.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...forms/200912/1

  #8  
Old December 15th, 2009, 01:20 PM posted to microsoft.public.access.forms
JamesJ[_5_]
external usenet poster
 
Posts: 32
Default Record Corruption

I'm considereing changing the field(s) back to plain text but need to remove
any formatting or the formatting "characters" will carry over in the plain
text.

Thanks,
James

"Linq Adams via AccessMonster.com" u28780@uwe wrote in message
news:a09a9ffad6765@uwe...
To add to the mix, RTF, in v2007, is actually stored as stores HTML, which
may, in fact, add to the chance of corruption.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...forms/200912/1

  #9  
Old December 15th, 2009, 11:45 PM posted to microsoft.public.access.forms
David W. Fenton
external usenet poster
 
Posts: 3,373
Default Record Corruption

"Arvin Meyer [MVP]" wrote in
:

The problem occurs because it is an OLE field. Other OLE fields
and the Hyperlink field are prone as well.


....and the Hyperlink is prone because hyperlinks are actually stored
as memo fields (so it's not two problems, but just another
manifestation of the same one).

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
  #10  
Old December 15th, 2009, 11:49 PM posted to microsoft.public.access.forms
David W. Fenton
external usenet poster
 
Posts: 3,373
Default Record Corruption

"JamesJ" wrote in
:

I also found the following to be useful.

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


Overall a fairly good article, but I stumbled over this advice:

store them in a separate backend database

....as a way of avoiding problems with memos. I wonder if the person
writing the article is an xBase refugee, where each DBF file is a
data table and referred to colloguially as a "database," even though
it's actually a data table.

The advice as it stands is insanely wrong, as there's absolutely no
danger of a corrupted memo pointer in one table in an Access data
file somehow polluting the other tables and corrupting their data.
So, I'd definitely change that advice to:

store them in a separate data table

....which will be sufficient to isolate memo corruption from the main
data records.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 06:25 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.