>>Harry,
>>
>>You can only say "Stop!" if something somewhere knows what to stop and how to stop it. IOW, you need a framework that keeps track of everything that occurs in the app so it can shut down whatever is running. There are some public domain frameworks available, check the libraries here. There are also some commercial frameworks that sell for around 400-500 dollars. Keep in mind, you get what you pay for.
>
>hmmm...
>seems a retro step to me. Why can't we just (still) say 'close any windows, clear any forms,shut down anything thats open, clear any variables from memory,shut any open databases, clear the program buffer etc etc and goodnight!'? What changes have taken place in VFP which prevent what was perfectly possible in 2.6?

Object orientation, database integrity enforcement, data buffering, private data sessions, etc.. All of these need to be resolved. You need to make sure all objects are released from memory. If any object has data buffered it will put up a dialog for the user to decide whether to save or revert the buffer.

This is not backward, it is forward from a procedural language that required programming backflips to handle multiple windows open at once to an object oriented system where each form is its own object with its own state which is maintained without programmer intervention.

Try opening two copies of a customer form in FPW 2.6. I used a technique for doing that but it was certainly not pretty. In vfp I can let the user open as many copies of the customer form at once as they like. Each form will have its own data and its own state without any code on my part.