I'm currently building up a database, and want to improve the way I'm handling the memo fields. I'd thought I'd planned for it fairly well, but had the first corruption problem at about 750 records.
Right now, I'm simply using a bound text box with the underlying table as a record source for the form. I've gone back and split the underlying table out into a separate table with a one-to-one relationship and populated it using an append query. It would be simple at this point to switch the underlying row source to a query that pulls in the new table and keep running it basically as is. However, I'm not sure if that really helps me because I don't understand the corruption problems that come from those memo field pointers well enough to know if modifying the database design like this is sufficient to protect against corruption.
Is it a good idea to set up that field as an unbound box that populates using the new table, and if so how do I code the operations the bound form usually handles automatically (populating and updating existing records, or adding and saving new ones)? I'm reasonably comfortable working with VBA, but this isn't something I've tried to do before and if just using a query to incorporate the second table is workable to stabilize this memo field I'll happily do that.
Right now, I'm simply using a bound text box with the underlying table as a record source for the form. I've gone back and split the underlying table out into a separate table with a one-to-one relationship and populated it using an append query. It would be simple at this point to switch the underlying row source to a query that pulls in the new table and keep running it basically as is. However, I'm not sure if that really helps me because I don't understand the corruption problems that come from those memo field pointers well enough to know if modifying the database design like this is sufficient to protect against corruption.
Is it a good idea to set up that field as an unbound box that populates using the new table, and if so how do I code the operations the bound form usually handles automatically (populating and updating existing records, or adding and saving new ones)? I'm reasonably comfortable working with VBA, but this isn't something I've tried to do before and if just using a query to incorporate the second table is workable to stabilize this memo field I'll happily do that.