>Jim,
>
>>The GetNextModified() function may be helpful here.
>
>According to help, The GetNextModified() works only if you use tablebuffering.
>Tablechanges of non-buffered tables within a transaction cannot be detected in this way.
>
>
>James,
>
>May its wise to enable tablebuffering for all tables within a transaction and update these table with Tableupdate just before commiting the transaction.
>
>You may need some error handling when the tableupdate fails.
>
>Walter,

Thanks for the tip. Error handling may resolve my issue. The problem is that foxpro is acting as a server here (west wind) and handling various requests. I shut down the server and there is outstanding transactions. So who is the bad boy? Somewhere a program allows itself to be exited without rolling back or committing. I know that the error handler is a bad boy (we are in process of writing the error handler) but then I can't prove it's the error handler -- it could be some other process... If I could identify the tables involved I could identify the process... naja. moan complain...

Jamie Beerbower