I wasn't sure whether to post here or in the Access Forms forum, but I have a suspicion that if this can be done at all, it will need to be done in code...
I have a form on which all fields are locked except one, which is a "notes" field (memo format). I want all users to be able to add notes to the field. However, once a note is added and the record saved, I want those existing notes to be protected. I'd like other users (or the same user) to be able to enter the record later and add subsequent notes to the same field (creating a cumulative memo field of notes), but I don't want anyone to be able to delete existing notes. I've read about creating separate tables with audit trails of changes/deletions, but this is really not what I'm looking for. I basically want to keep all of the notes in the field, but not allow anyone to (accidentally or intentionally) delete out existing notes to "revise history", so to speak. The memo field is not to be used for any data mining, etc., so I don't care if it gets messy because of users' inability to delete. It's simply a method of creating subjective status reports.
Any thoughts would be appreciated.
Thanks,
Patricia
I have a form on which all fields are locked except one, which is a "notes" field (memo format). I want all users to be able to add notes to the field. However, once a note is added and the record saved, I want those existing notes to be protected. I'd like other users (or the same user) to be able to enter the record later and add subsequent notes to the same field (creating a cumulative memo field of notes), but I don't want anyone to be able to delete existing notes. I've read about creating separate tables with audit trails of changes/deletions, but this is really not what I'm looking for. I basically want to keep all of the notes in the field, but not allow anyone to (accidentally or intentionally) delete out existing notes to "revise history", so to speak. The memo field is not to be used for any data mining, etc., so I don't care if it gets messy because of users' inability to delete. It's simply a method of creating subjective status reports.
Any thoughts would be appreciated.
Thanks,
Patricia