Wayne <cq*******@volcanomail.comwrote in
news:49**********************************@i24g2000 prf.googlegroups.co
m:
I've been asked to construct a database which will require several
memo fields. This database will be the standard frontend/backend
mdb configuration. I have read many posts describing the
corruption problems associated with memo fields, especially in a
networked environment. Am I asking for trouble if I go ahead with
this project?
You might want to try one of three approaches (or a combination of
them):
1. store your memos in a separate table, with a 1:1 join between
your memo table and your table for the rest of your data. If a memo
pointer gets corrupted, you won't lose any data in the main table.
2. store your memos in a separate table, 1:N, where each record in
the memo table has a memo type (assuming you have more than one memo
field).
3. edit your memos with unbound controls. To do this, you read the
memo value from the form's recordset into an unbound textbox in the
form's OnCurrent event, and then save edits to the textbox back to
the underlying recordset in the textbox control's AfterUpdate event.
Those are the steps that can be taken to minimize the possibility of
memo corruption, and I think they work pretty well.
--
David W. Fenton
http://www.dfenton.com/
usenet at dfenton dot com
http://www.dfenton.com/DFA/ 
