>>>>>>>I am getting different results when I run the same prg:
>>>>>>>-from within a form
>>>>>>>and
>>>>>>>-at the command prompt
>>>>>>>
>>>>>>>Is there any logic to this?
>>>>>>
>>>>>>And what is the difference?
>>>>>
>>>>>It's a financial that tallys and compares a table vs another etc. It sends the output to a file for viewing, and running it from the cmd prompt renders correctly, thru the form, alot is blank.
>>>>
>>>>If there is printing involved and there is a grid on the form, then it could be a problem.
>>>>
>>>>Also there may be difference in SET ANSI/SET EXACT/SET DELETED in the form and your environment.
>>>
>>>That's it!! thanks. the exact was getting reset to 'on' somewhere along the way. Who knows how many hours you saved me!!
>>
>>Umm. That's what I told you.
>
>You mentioned to check my prg but there was no reference to a "set exact" there. I checked the form and there was no setting there either. The setting of exact is set to "off" in the previous form, then when this form activates, the setting changes to "on". I am trying to figure how this occurs.

Reread what I wrote. :) Private data session FORMs can have different SET ings from the command window. If your first form has a private datasession the default is SET EXACT OFF. If the second form is default it "inherits" the settings from the first form.

HTH