David, thanks for your reply.

I'm not sure if I follow you .

Are you suggesting having One Form, but with 4 pages which will contain each of the controls from each form: (Sounds like this might work)
i.e. Page 1 has the controls for Forma
Page 2 has the controls for Formb etc

If this is the case, I dont follow your point where One form 'Launches' another form ...wont there be just One form in this scenario ? (but with 4 pages)

Regards,

Gerard





>Gerard,
>
>I'd throw two other suggestions out
>
>1) use a 4 page pageframe, putting the controls from each screen on each page
>
>2) Have FormA (forms are the VFP name for 2.x screens) run in a Private data session. Then set the other's forms to Default data session. When FormA launches FormB it'll be running inside the private DS of the parent form. Then when FormB launches FormC it'll also be in same DS. This will let all of the forms see the same tables/cursors.
>
>>I'm in the process of upgrading / rewriting an old APP that was in FPW 2.6.
>>This app has a load of screens which work as follows:
>>
>>ScreenA calls
>> ScreenB calls
>> ScreenC Calls
>> ScreenD etc
>>
>>
>>i.e. I have a screen which calls a screen which in turn calls another screen etc
>>
>>ScreenB, ScreenC and ScreenD will need access to variables that are created in ScreenA.
>>In FPW , I did this by initializing Variables in the Screen Setup , and once this was done, they persisted locally for ScreenB,ScreenC and ScreenD also