|
| 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. |
|
|||||||
|
|
|
Thread Tools | Display Modes |
|
|
|
#1
December 14th, 2009, 07:43 PM
posted to microsoft.public.access.forms
|
|||
|
|||
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
December 14th, 2009, 08:44 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
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
December 14th, 2009, 09:48 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
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
December 15th, 2009, 11:22 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
Record Corruption
James
Any chance there's a wireless LAN involved here somewhere? That can also cause problems... Regards Jeff Boyce Microsoft Access MVP -- Disclaimer: This author may have received products and services mentioned in this post. Mention and/or description of a product or service herein does not constitute endorsement thereof. Any code or pseudocode included in this post is offered "as is", with no guarantee as to suitability. You can thank the FTC of the USA for making this disclaimer possible/necessary. "JamesJ" wrote in message ... 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
|
|
#5
December 17th, 2009, 04:38 AM
posted to microsoft.public.access.forms
|
|||
|
|||
|
Record Corruption
"Jeff Boyce" wrote in
: Any chance there's a wireless LAN involved here somewhere? That can also cause problems... ....and, of so, you shouldn't be using Access across it with a Jet/ACE back end, as that way lies madness (and perpetual corruption). WiFi is simply not reliable enough for use with Access, unless you're running the app on a remote terminal server, or if your back end is SQL Server or some other server database, where all the data processing happens on the server. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
|
|
#6
December 19th, 2009, 02:42 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
Record Corruption
Nope
"Jeff Boyce" wrote in message ... James Any chance there's a wireless LAN involved here somewhere? That can also cause problems... Regards Jeff Boyce Microsoft Access MVP -- Disclaimer: This author may have received products and services mentioned in this post. Mention and/or description of a product or service herein does not constitute endorsement thereof. Any code or pseudocode included in this post is offered "as is", with no guarantee as to suitability. You can thank the FTC of the USA for making this disclaimer possible/necessary. "JamesJ" wrote in message ... 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
|
|
#7
December 14th, 2009, 10:08 PM
posted to microsoft.public.access.forms
|
|||
|
|||
|
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
|
|
#8
December 15th, 2009, 01:23 AM
posted to microsoft.public.access.forms
|
|||
|
|||
|
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
|
|
#9
December 15th, 2009, 02:17 AM
posted to microsoft.public.access.forms
|
|||
|
|||
|
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
|
|
#10
December 15th, 2009, 02:39 AM
posted to microsoft.public.access.forms
|
|||
|
|||
|
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
|
|
| Thread Tools | |
| Display Modes | |
|
|
Hybrid Mode
