Tom,

>I suppose I could possibly scan this second cursor for changes manually and create the SQL Updates in code, but that seems like it could be slow.

I chose this technique and performance is not an issue. I'm doing all of my updates with stored procs so scanning the update cursor was necessary anyway.

Also keep in mind that SQL Server does not have an empty {} value for datetime like VFP. So you have to look out for NULL datetime values.