Dan,

Ok, I've figured out why it behaves differently when I "do main" vs call the form standalone. "Do Main" uses the default settings from the goapp object, of which SET DELETED ON is one. When I call the form standalone, it gets the VFP default of set deleted (which is OFF) when the private data session is established, and as it is standalone, the goapp object doesn't exist to provide a default of ON for SET DELETED, so it stays off.

At this point, my code is working the way I want, so that is good enough. I've changed so many things that I don't remember which one made it work. It could have been Laura's suggestion about the zorder of the bizobj and sessionEnvironment. I know that one bit me a few times in the early development, but I thought I had it right when I tested this form, and don't remember changing the order after that.

Thanks to all for their help.

June

>June,
>
>I set deleted off in the command window. I opened up the debugger and set a break on SET('DELETED') and ran main. The break happens in the set method of aglobalenvironment.osessionenvironment. The default code of the addchildren method of the application object calls This.CreateGlobalEnvironmentObj(). I'd make sure you are doing a DODEFAULT in the addchildren method of your application object.
>
>HTH
>
>-Dan
>
>>Where does MM default to deleted on? If I set deleted on at the command line, then call my form via createobject, and stop at a breakpoint in the form load method, deleted is already off there. If I step through the load routines, including the oSessionEnvironment Set method, deleted never goes back on.