Memo fields in separate tables

[mhart]

I have an Access 2010 database with two of the many tables having several memo fields. The database has been split, with the backend on our network and frontends on each person's computer (total of 5 users). Through our testing efforts, one of the memo fields became corrupted (two different times). I've researched corruption and found in "Implementing a Successful Multiuser Access/JET Application" that I should "consider isolating Memo....data types in separate tables with a 1:1 relationship..." I've experimented and found that I can export an existing memo field into a spreadsheet and then import it into a new table in the database, but this would mean completely redesigning the forms. My question is, is it worth the time and effort? Has anyone done this and solved a memo field corruption problem? Or is there a better way to solve the problem?



Thanks,
Marilie

[ajetrumpet]

I've experimented and found that I can export an existing memo field into a spreadsheet and then import it into a new table in the database, but this would mean completely redesigning the forms.

Why would that require new forms? Consider:

• Export table
• Delete original table
• re-create table definition
• import memo field back in

If you have the same table with the same name in the end, why new forms?

Plus, doing it with xls requires much more resource than doing it with txt. Txt might offer less headaches.

And I believe, but not positive, that corruption usually occurs on a level. For instance, a field (maybe a prop or some data bytes), a table, or the database as a whole.

Hence, if a field is corrupted, export not necessary. If table is corrupted, export probably necessary.