PMFJI, but you can also use an Application object to store this information. Then the form in it's Load() can send a message to the application asking, "What's going on?" If you run the form by itself, with no application object going, it does some default behavior. If the App is instantiated, it gets direction/information from it.


>>>You can pass parameters to the form that are received in the forms init
>>
>>You can use the call stack, but if I were to vote, this would be the best method, to recieve a parameter indcating the "mode" the form is in and then save it to a property for later use.
>
>I'm of two minds here. Sometimes when I want a reference to the calling form, I will pass it as a parameter. Sometimes, I will rely on _SCREEN.Activeform in the load of the Called form. But since I've found that _SCREEN.Activeform is not so reliable, I prefer the explicit passing of the reference to the form.
>
>As far as program() is concerned, I believe one advantage would be that you could use that information in the load instead of waiting until the init, but again you are relying on the call stack instead of explicitly passing it which may be safer.