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
  #21  
Old December 18th, 2009, 04:55 PM posted to microsoft.public.access.forms
Jeff Boyce
external usenet poster
 
Posts: 8,621
Default Record Corruption

James

In my neighborhood, I can count on the power "flickering" several times each
year. In fact, "flickering" is much more frequent than full-blown power
outages.

Is your PC on a UPS?

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
...
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



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

in-line:

"JamesJ" wrote in message
...
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?


No, only the one beign written to, or at worst several records on the same
data page.

I'm not on a network and don't share the db with anyone and
I have no settings allowing my computer to sleep.


That could be a function of the hard drive. "Green" computers often have
hard drives that spin down when a computer hasn't been used for several
minutes.

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?


I only use the MDB format so that it's compatible with other versions.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com


  #23  
Old December 18th, 2009, 09:22 PM posted to microsoft.public.access.forms
JamesJ[_5_]
external usenet poster
 
Posts: 32
Default Record Corruption

Although I'm not familiar with electrical stuff, my power must be
"flickering" more now that I'm running ac 2007 as apposed to when I was
running ac 2003.?

James

"Jeff Boyce" wrote in message
...
James

In my neighborhood, I can count on the power "flickering" several times
each year. In fact, "flickering" is much more frequent than full-blown
power outages.

Is your PC on a UPS?

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
...
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



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

"JamesJ" wrote in
:

In fact when the memo field gets corrupt I'm able to copy the
contents of the memo field to the clip board delete the data form
the memo field at the table level and then paste it beck.


If you can do this, then it's not the same kind of memo corruption
as we saw in previous versions of Jet. Is this an ACCDB or an MDB?
If the former, is it an append-only memo field?

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

"JamesJ" wrote in
:

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.


Are you running AV software?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
  #26  
Old December 19th, 2009, 03:17 AM posted to microsoft.public.access.forms
JamesJ[_5_]
external usenet poster
 
Posts: 32
Default Record Corruption

I was runnning Microsft Security Essentials, now
I have AVGFree installed.

James

"David W. Fenton" wrote in message
36.94...
"JamesJ" wrote in
:

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.


Are you running AV software?

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


  #27  
Old December 19th, 2009, 03:41 PM posted to microsoft.public.access.forms
JamesJ[_5_]
external usenet poster
 
Posts: 32
Default Record Corruption

ACCDB

"David W. Fenton" wrote in message
36.94...
"JamesJ" wrote in
:

In fact when the memo field gets corrupt I'm able to copy the
contents of the memo field to the clip board delete the data form
the memo field at the table level and then paste it beck.


If you can do this, then it's not the same kind of memo corruption
as we saw in previous versions of Jet. Is this an ACCDB or an MDB?
If the former, is it an append-only memo field?

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


  #28  
Old December 19th, 2009, 03:42 PM posted to microsoft.public.access.forms
JamesJ[_5_]
external usenet poster
 
Posts: 32
Default 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




  #29  
Old December 20th, 2009, 12:31 AM posted to microsoft.public.access.forms
David W. Fenton
external usenet poster
 
Posts: 3,373
Default Record Corruption

"JamesJ" wrote in
:

"David W. Fenton" wrote in message
36.94...
Is this an ACCDB or an MDB?
If the former, is it an append-only memo field?


ACCDB


Uh, well, what about the follow-on question?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
  #30  
Old December 20th, 2009, 01:36 PM posted to microsoft.public.access.forms
JamesJ[_5_]
external usenet poster
 
Posts: 32
Default Record Corruption

Sorry didn't read far enough.
I really don't know.
I've looked at the properties of the memo and see no property for Append
Only.
Where might I find that property?

James

"David W. Fenton" wrote in message
36.89...
"JamesJ" wrote in
:

"David W. Fenton" wrote in message
36.94...
Is this an ACCDB or an MDB?
If the former, is it an append-only memo field?


ACCDB


Uh, well, what about the follow-on question?

--
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 09:06 AM.


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