>Andy,
>
>What is your goal here? Objects exist and as long as they exist they are visible to your code by using their name and containership. If you assign them to a variable that variable follows all the rules of scoping of variables.

I do a lot of report work inside some elses application. They allow
someone to write reports in a separate data session. My concern is if I create
a form for imput of report specs, such as date range, customer range, etc..,
that an object my have the same name as other object already in the system that I am not aware of.

I have always declared all variables that I use as private just to cover myself.
Now that I am starting to create forms instead of 2.6 screens that the object in that form, or the form itself may conflict with others in the application.


Another questions is:
If I create an object in the form and then call a report in that form
is there a way to use that object value to the report other than
passing a value from the object to a variable

m.lcvariable=THISFORM.StartDate1.VALUE

and using m.lcvariable in the report

or using the object name

THISFORM.StartDate1.VALUE

in the report itself?