While memo fields are slightly more likely to corrupt than text fields, this
is not a major factor in a well designed database. We use memo fields in
almost every database we write.
Just take the normal precautions to avoid corruption:
- Make sure your database is split (front end on each work station; shared
back end on server).
- Make sure all workstations have the latest Office service packs applied.
- Make sure the power, network, workstations are all reliable (not
crashing/intermittent) and users log off properly (don't just switch off).
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Reply to group, rather than allenbrowne at mvps dot org.
Clarissa said:
We have a database with multiple users updating different records in the
same table, and would like to avoid record locking problems. A couple of
items I've read say that Memo fields should be avoided. But, my problem is
that all of my tables/forms have at least one memo field. Unfortunately, we
can't avoid it. Any tips for this situation? If no technical workaround,
does anyone have suggestions for how to manage user expectations and/or deal
with the anticipated locking problems?
