**Thanks for your input Mark. Unfortunately, our framework does not have an App object. However, each form usually has a calling program. Those programs could define vars that the form could reference (although I really didn't want to work that way).**

Just because your framework doesn't have an App object is not a reason for not using one.

It would be fairly simple to have one and to instantiate it at the start of the app.

Then prior to DO Form an oApp.CallingProgram property can be set for reading in the Load of the form.


**I did realize, though, (after my post) that I may be able to code the name of the program into the form property at design time rather than passing it. I was assuming it had to be passed simply because that's what we had been doing. That in itself would solve our problem.**

You could do this. But if you know at design time the name of the program calling the form I do not see why you have a problem. You can code it into the Load event.

I assumed that a form could be called from different programs - which would require the need of parameters.

Andrew R.