G
Guest
Hello everyone,
I would like to setup my main form so that if I am making any change(s) to a
record, that record would first be saved in a separate table before
modifications, and again after such mods.
This second table would first identify the ID of the current record, the
username of the person making the modification, the date of the
modification(s) and then the whole record as it is before the modification,
and finally the whole record again as it is after the modification.
I thought that saving the whole record would be easier to program/implement
than if I were to try saving only the field(s) modified, though if someone
thinks that it would be just as easy to save only the modified field(s), then
I'm listening.
What commands would I use to accomplish this? Would I have to set the
OnDirty event for every field? If I had to use this event, can I get it to
save the existing/current value in the field before any mod is done? As the
name implies, an event action would only be triggered once I'd done some sort
of mod, no?
The purpose of all this is for me to be able to quickly verify all changes
made to the database by our new secretary. Since I don't have much time
during the day to monitor and explain the proper handling of the data to her,
I can check in the evening or during slack times what changes were done, what
notes were added, and suggest improvements or corrections where appropriate,
without worrying about the database becoming a fair bit contaminated before I
start spotting problems/inconsistencies/errors/duplicates, etc. Secondly,
when any record is found faulty in the future, for any reason, one can go
back through all the history and determine where the error was introduced,
and from there re-copy the data as it was before the error was made. This
would work as a great secondary backup for the database; it would allow
restoration of individual records rather than the whole database.
Any suggestions appreciated. Thanks.
I would like to setup my main form so that if I am making any change(s) to a
record, that record would first be saved in a separate table before
modifications, and again after such mods.
This second table would first identify the ID of the current record, the
username of the person making the modification, the date of the
modification(s) and then the whole record as it is before the modification,
and finally the whole record again as it is after the modification.
I thought that saving the whole record would be easier to program/implement
than if I were to try saving only the field(s) modified, though if someone
thinks that it would be just as easy to save only the modified field(s), then
I'm listening.
What commands would I use to accomplish this? Would I have to set the
OnDirty event for every field? If I had to use this event, can I get it to
save the existing/current value in the field before any mod is done? As the
name implies, an event action would only be triggered once I'd done some sort
of mod, no?
The purpose of all this is for me to be able to quickly verify all changes
made to the database by our new secretary. Since I don't have much time
during the day to monitor and explain the proper handling of the data to her,
I can check in the evening or during slack times what changes were done, what
notes were added, and suggest improvements or corrections where appropriate,
without worrying about the database becoming a fair bit contaminated before I
start spotting problems/inconsistencies/errors/duplicates, etc. Secondly,
when any record is found faulty in the future, for any reason, one can go
back through all the history and determine where the error was introduced,
and from there re-copy the data as it was before the error was made. This
would work as a great secondary backup for the database; it would allow
restoration of individual records rather than the whole database.
Any suggestions appreciated. Thanks.