Thanks for the explanation. Basically all rows (except 3 header rows) will have form fields... It might be possible, that the user will fill it out (filling in fields in all rows), and then come back later and have to delete a row (in which case I figured if they deleted the information in the form fields, then the macro would delete the row for them when they exited the table). Perhaps my thinking is wrong. I am working with ‘practically’ computer-illiterate users, so I try to make things fool proof. In doing so, I may be the fool. I am contemplating removing all form fields from the table, making those rows of the table a separate section, and leaving those rows of the table unprotected in the document, so the user can manipulate as needed (this may backfire on me in the end too.)
|