Memo Field has issues

[knawtn via AccessMonster.com]

Hello. This is my second posting for this issue....first in "Forms"...now in
"Database Design".

I have a table containing accident report data. One field, AccDet, is a memo
field for accident description/details, and can be as many as 1000 characters
in length. I have a form, tied to the table, where this data is filled in. No
problem........until I close the form and open the table. The memo field has
the first 500 +- characters accurate...then some kind of weird symbolic code-
gibberish-gooble-d-glop replacing the last part of the memo field.

I also created an edit form, based on a query that is based on the table.
When I choose the questionable record, it displays in the same manner on my
edit form. However, when I replace the garble-splop with the correct text, it
saves fine (from the edit form).

Fortunately, I have only just begun. Only 4 records of test data thus far.
Already compacted (Access 2003). Already re-created and imported. Same
results.

DB sits on a network share, but has only been used by me so far.

Strange one. Any help?

 

[Guest]

One of the weaknesses of Memo fields, and there are many, is that they
corrupt frequently. Sounds like that might be your problem.

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

If this a mission-critical database (i.e. you could lose your job over it) I
highly recommend not using Memo fields. If you need more than the 255
character in a Text field, consider moving to another database such as Oracle
or SQL Server, where the text fields can have over 1,000 characters.

 

[knawtn via AccessMonster.com]

Thanks.

I tried several of the suggestions...to no avail. Memo field from the form
types in without a problem, but then it gets blasted somewhere between the
append query and the table it's being appended to. But adding data to the
memo field directly in the table works fine. Unfortunately this does not suit
my design.

Maybe after a quit smashing my skull against my keyboard I'll re-design this
thing and skip the append. Seems as though the Gates family would have a fix
for this issue.

I have a few ideas I'm working on, and I appreciate the advice.