>>Some options on what to do if the user has the current record edited but not saved.
>>It might save the record automatically (or cancel changes if does not pass validation) or optionally show the normal dialog, prompting the user to Save/Cancel. Of course, if the user is away from his desk, the app will stay running, but then our Help Desk may call them and ask to close app. Some users in corporate world are not happy when somebody just kills their changes and we have to deal with it. :)
>
>Nick,
>
>Are you comparing the existing record with a buffered one to determine what needs to be done?
>
>Renoir
I don't add this comparing functionality, I just tap into the existing Save/Cancel functionality of the framework. Depending of the shutdown option it makes the choice to kill the user or let him live. :)
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison