M
Maury Markowitz
This is a little more complex than it might sound at first glance.
I have two tables that are identical, one is tblOrders and the other is
tempOrders. To edit a record in tblOrders I first copy it over to tempOrders
and do all the work there. That way if the user Cancels out or there is some
sort of error, the original data is untouched.
If the user does decide to Save their changes, I open a recordset back into
tblOrders (I have the original ID in temp), and then loop over the fields in
tempOrders and copy them back into tblOrders. Then I call .Update on the
tblOrders recordset.
But now I want to attach triggers to the table to track changes. I don't
want them to fire if nothing actually changed. IE, if the row in tempOrders
is identical to the original (which it will be something like 50% of the
time), nothing should happen. Assuming that every field is the same, does
..Update do anything?
Maury
I have two tables that are identical, one is tblOrders and the other is
tempOrders. To edit a record in tblOrders I first copy it over to tempOrders
and do all the work there. That way if the user Cancels out or there is some
sort of error, the original data is untouched.
If the user does decide to Save their changes, I open a recordset back into
tblOrders (I have the original ID in temp), and then loop over the fields in
tempOrders and copy them back into tblOrders. Then I call .Update on the
tblOrders recordset.
But now I want to attach triggers to the table to track changes. I don't
want them to fire if nothing actually changed. IE, if the row in tempOrders
is identical to the original (which it will be something like 50% of the
time), nothing should happen. Assuming that every field is the same, does
..Update do anything?
Maury