>I have an app with many forms, and many buffering modes. Not every form will have the same buffering modes established, some (opt 3)
> and some (opt 5) and some nothing at all. In order to assure that the current forms buffering is set correctly, I am with the understanding that I need to either use private DS's with the buffermodeoverride set to the appropriate mode, or set buffering in code (possibly activate event) to assure that when a form is the active form the correct mode, if any, is set. What is generally the best approach, and if Private data sessions is the way to go, am I opening a can of worms for the rest of my app that private DS's will agitate. The reason I say this is that I simply switched to private DS's in my main form and weird things started happening. It almost acted as if talk was set to on which completely covered my open form with what looked to be the values of objects being instantiated for the active form. Also, after that was finished, none of my tables were in my forms Data Environment were opened, they had all closed. Sorry for the long winded message, and any tips/suggestions
>appreciated. Thanks!!

AFter reading other replies to you, I have one more. Create a Form subclass with its datasession set to private and put all your SET commands in the load event. In my form subclass the last command in the Load event is THISFORM.ADDLOAD() which is a custom method of the subclass where I put additional code at design time. Otherwise, if you put code in the Load method when designing, you always have to remember to use the scope resolution operator (::) to execute the parent class code. VFP5 has DoDefault as an alternative to scope resolution. I tend to forget to do this, so I use the AddLoad for additional code. Thanks to Barbara Paltiel for this idea.