Joel,

I had the same situation once before and I had to change my application to use modal forms in that case. Perhaps, this is my only choice here too.

I can use pathing suggestion and leave form to be modeless, but it will leave a room for error, if I have two versions of the report in the path.

I'll also can make Form state to be conditional.

Thanks.


>>>Nadya,
>>>Just a guess.
>>>What happens if you add the AppB directory (and its subdirectories if necessary) to SET PATH instead of SET DEFAULT?
>>>
>>
>>In our set path we use relative paths, e.g.
>>Reports,Forms,Data, etc.
>>IOW, each time, we invoke an application, we should set default to this application directory in order to all subdirectories on this application be seen.
>>
>
>Hi Nadya,
>
>It seems like this would cause problems when using modeless (non-modal) forms. If you were able to SET DEFAULT TO the AppB directories, then AppA would not be able to see them. My guess is that AppA is expecting your form to be modal. Does the AppA code calling AppB look something like this?
>

>set default to &ApplBPath
>Do AppB.app
>set default to &ApplAPath
>

>
>If so, your modeless form never stops program execution, and the default path gets set right back to AppA. HTH.