memo field corruption

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

HI
I developed an app (Ac2000/FE/BE) some time ago and all was fine.

Suddenly the BE is getting corrupted when updating a memo field. I've tried
updating via ADO CMD object, Docmd.runsql and now via an ADO recordset. I've
seen some postings that suggest problems when memo size gets over certain
number of chars. That sound correct because some records now have large
(<2K)ammounts a data in the memo field and they are the one giving the
problem, smaller size fields work fine.

Anyone got any input, workarounds etc.

regards


walter
 
I've seen this and it is a known issue..best workaround is to compact and
repair regularly (compact on close and/or schedule process).
You can also use multiple text fields (which is safest way).

Bob
 
Thanks for the response.

repair is inpractical, the field is being edited continually. Multiple text
fields? .. I feel quite sick thinking about that ..

I'll wait to see any other ideas, where is MS on this one?
 
Hi Wally,

Access/Jet databases aren't designed for 24/7 availability. You have to
get all the users out of the back end in order to get a reliable backup
or to compact-and-repair.

If users need round-the-clock access, you need to move the back end into
a server-side database engine such as SQL Server (there's a free version
available).

Meanwhile, I don't think you have any alternative to shutting the
database down while you repair the back end, or restore it from backup
(assuming that you have a working one).
 
That's odd, I haven't seen any memo corruption for years - since
Jet 3.5 sp3. What format are you using for your data files (are
you sure that they are not A97 compatible)?
 
Thanks for the responses on this one.

First Jon:
Sorry for the misunderstanding, its not a 24/7 situation - I meant that
every time the guy edits the data (on certain records) it corrupts, so he
would need to repair on every edit.

David:
The app was dev in Acc2K but is now used by Acc2003, but in Acc2K file
format. I still edit the code in Acc2K.

Anyway, I appear to have found the problem. The memo field had an index on
it but I never put it there.Does Acc2003 auto create indexs?
I found a KB (302525) that references this. I deleted this and all is OK.
Comments appreciated.
 
Access automatically creates indexes if you use Access
to create the table or add a field.
Tools, Options, Tables/Queries:
"AutoIndex on Import/Create"

Also when you create relationships you get FK indexes.
(you shouldn't create relationships on memo fields)

BTW, Anything that implicitly or explicitly groups by
memo fields (including DISTINCT and UNION queries)
can also give you corrupt memo field values.


Thank you for posting back with the solution

(david)
 
I have this same problem still. I'm glad to find that someone actually found
a solution. However it isn't the solution for me does anyone else have ideas
what could cause this? It worked 2 weeks ago. If it makes a difference I
am working with a replicated database with FE and BE.

It only happens if the Memo size is really big, but nothing more than the
65,536 characters that the API states as the Max for Memo fields. But if I
update it with just 1K of characters it seems to work fine. I need to be
able to store larger memos than 1K characters.
 
Back
Top