>>>I have two forms for my stock transaction history. One form is for the user to select the stock and the other form is to display the transaction history for the stock. At the moment, I am using a formset. I don't really like it because if I have different format of the transaction history form, I need to have many forms in the formset. It seems to slow down the whole thing.
>>>
>>>My question is: can I use 'do form txnhist' in my first form (the select stock form)? My problem is if I set up my data environment in the first form, open the second form without closing the first one, the second form doesn't use the table open in the first form.
>>>
>>>I know that I can make the second form a class and instantiate it. But it seems stupid.
>>>
>>>What is the usual way? Can anyone share?
>>
>>
>>I can also use parameterized view for the second form. Any other option?
>
>If second form has default data session it will use tables opened in the first form, if it's private data session then you have to create and use separate DE.
>Both ways are feasible and widely using.

Another option: if the first Form has a private data session you can also pass to the second form the parameter THISFORM.DataSessionID and in the init of the second Form issue SET DATASESSION TO (pn_parameter).

Just remember that into the second Form the tables won't be "visible" until you issue the SET DATASESSION...