Why not let the front-end cache the changes and push them out in (one transaction) only when the user decides to save?

-Mike

>I am having a tough time trying to write a stored proc to backup the many child tables into another database when a customer clicks 'edit' on the parent (in a VFP Front end). I need this so that if the user clicks 'cancel' that another stored proc would restore the child records back to the way they were. If the user clicks save, nothing extra happens.