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.
Most of this data comes from my dvd library and the dvds that are tv shows
with many show titles and descriptions and I'm cramming all the information
about the dvd into the memo field.
So a text field wont get it. 255 characters doesn't go very far.

Also I know I believed I asked this in this thread but before I make any
rash
changes to my db I want to find out if anything can be done to actually
minimize the chance of corruption in memo fields.

1) It appears that a large amount of data in memo fields seems to promote
corruption.
Are my observations true?
2) If I use only plain text as apposed to rich text, will that minimize the
chance for corruption?

James

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

I'm assuming you mean I should create a new db and store
the rich text memo field(s) there?

No, not at all. The whole point of my post was to emphasize that you
don't need a new back-end database, but just a new table in the same
back end.

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