>Unfortunately, the situation is not really could be called 'disagree'.

Ed,

In my situation it is disagree strongly, very strongly. I personally feel that your recommendation of this 2.x approach of doing things in VFP is a disservice to the new folks here trying to learn VFP. It suggests that they should write a boat load of code to do what VFP can do for free.

Your approach of using the Activate event to reset the data environment of a form is a poor man's private data session. Your refusal to use data buffering also requires you to write code to handle the discarding of changes when VFP would be perfectly happy to let you use TableUpdate to save and TableRevert to discard.

Having every form share the same data session when each form can have its own data session is simply a break in encapsulation where it is not necessary. I haven't seen any advantages to your approach. Everytime you have posted an explanation of how it works it has been a description of code you wrote somewhere to do what VFP can do without any code. You've, in essence, created your own version of private data sessions without using the PDS in VFP.

I guess I'm just from the old school that says if I write no code then I create no bugs. I will always choose the way that takes the least amount of code to accomplish a task.