Record Corruption

[Jeff Boyce]

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.

 

[Arvin Meyer [MVP]]

in-line:

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.

 

[JamesJ]

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

 

[David W. Fenton]

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]

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?

 

[JamesJ]

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

James

 

[JamesJ]

ACCDB

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?

 

[JamesJ]

Nope

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.

 

[David W. Fenton]

ACCDB

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

 

[JamesJ]

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]

I've looked at the properties of the memo and see no property for
Append

If you haven't explicitly set it up as append-only, it won't be.

 

[JamesJ]

ok

If you haven't explicitly set it up as append-only, it won't be.