Ed....

I know you will never engage in a technical debate, but....why would you go through all of this grief if private datasessions do all of the work for you? Tieing code to the activate event must make for some choppy interfaces. Sure, it sounds like you coded the heck out of it, and it may work for you. However, I would have to say that it is anything but a best practice. If anything, it is one of the farthest things from being a best practice I have ever heard. You said it yourself in a previous post in that you have taken a Fox 2.x methodology and applied it to VFP.

Please make a technical argument for why I should resort to 100's of lines of code that would be far less efficient and far more difficult to maintain than what VFP gives me for free....

Tell me this... lets say that one of your clients required the ability to make wholesale changes to a table, and at the user's descretion, abandon those changes and restore the values on disk. Since you do not use buffering, and the other data-related features as well, how would you implement this feature?

Cmon Ed, engage me in a technical argument here.....