Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Thoughts on a Screen calling a screen calling a screen
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00651233
Message ID:
00651869
Views:
11
Gerard:
Thjis is kind of 'out of the box'. You could make a 'grand' custom or form to contain your textbox values (keeping it INvisible), and then reference those for VALUE assignments on the desktop forms. (But) a DBF or CURSOR is also a container, and you could simply populate (by reference) the desktop forms with table field pointers.


>David,
>I was thinking more of placeholders to hold constants that would apply to all 4 forms that are calling each other.
>
>Typically, you might call up say the first form, and depending on this form (other than say data entry fields) you may want settings maintained/persisted and to be accessible by the called forms .
>
>Regards.
>
>Gerard
>
>
>
>>Gerard,
>>
>>I don't use memvars for data entry. I bind controls directly to table/view fields and use the native data buffering to be able to commit/revert changes. Using memvars ala FP2.x causes lots of problems when you consider multiple instances of a form.
>>
>>>In the Form calling a form scenario, I understand that the data can be common to all forms, bu Memory variables(or properties) initialized in say Forma wont be available in FormC ......
Imagination is more important than knowledge
Previous
Reply
Map
View

Click here to load this message in the networking platform