Dragan,

>> Just a WAG: why not do an implicit TableUpdate() on all the views, and wrap it all in a transaction - so if the user changes his
mind and abandons the whole three-generation-dynasty stuff, simply rollback. <<

Do TRANSACTIONS lock tables and/or records or generally do things we don't like to worry about any more with Optimistic buffering?

Also, although I am native VFP right now, will my BEGIN/END TRANSACTION be respected by Oracle or SQL Server when I upsize?