>>>Also controlling the scope of the variable, as in making sure it is local or private so it goes out of scope at the proper time would work.
>>
>>Thanks, my oApp.LoadForm() was defining that variable PUBLIC. I will try to define it PRIVATE instead and see if it goes out of scope.
>
>Let us (all) know the answer, Michel, since there have been several questions relating to this lately.

Well, I had a weird feeling about this and I just confirmed it.

The application object LoadForm() is now using PUBLIC (tcName) to make the object public before doing DO FORM X NAME (tcName). By putting PRIVATE instead of PUBLIC, the form appear and disappear right away and that's perfectly normal because once the DO FORM is finished, the LoadForm() will go away and so does the variable defined at that level.