Actually you're right. Putting SET TALK OFF in either the "load" or "init" seems to cure the "output" problem temporatrily. The 'hacking" is a program that ships with Visual Maxframe that allows the "on the fly" changing of the parent class of an object. Supposedly there is additional behavior happening, but I can't confirm first hand on this. But for the moment, only seems to be connected to VFP 6.0 and VMP 3.01


>>when these forms are called (all these instances have been from a menu hit), it starts to spit out properties of the form as well as various other output to anywhere it sees fit within the VFP main window. This has happened with 3-4 forms, once with me. Other programmers on this project have run into the same weird behavior, and the only solution was to copy the functionality of the old form to a new one(non-hacked). After this, the form works fine. Shrug, I have yet to figure out the reason for this behavior.
>>
>
>Sean,
>
>Sounds like talk is getting set on. What exactly is the Hacking you are referring to?