>>The client wants Private DataSession for the primary form because a Cust. Service Rep. (CSP) could be doing some posting work for Cust1 when a call comes in from Cust2.
>>
>>CSP selects Copy2 of Primary form (for ex. Telephone Log) to display/edit Cust2 info.
>
>By "Copy2", you mean a second instance of the primary form?

Yes, you are correct.

>
>>Cust2 wants to check production status on their order, so CSP selects Cust2 Production Form (Cust2 automatically comes up because it's using the same DataSession).
>
>Is the Production form called from a command button in the primary form or by an option in the menu? IMHO, since the Production form is dependant on the information from the primary form (in that case), the Production form should be called from the primary form. The primary form should pass the customer id to the Production form who should accept it and display the right record. This way, the Production form should run easily in a separate private datasession.
>

The Production form is called from Menu or Tool Bar. Command buttons on the Primary form is the way I did it in FPW 2.6a and it worked fine. I just wanted to use the Tool Bar in order to get rid of the 'clutter' on the Primary form. I'll try a command button on the form to see how it works. I guess I could still leave the Tool Bar buttons for when the Primary form is not open (i.e., posting batch receipts).


>>CSP finishes work on Cust2...closes forms, and returns to work on Cust1. This just seems to make things happen faster.
>>
>>If there is a better way to do this, I would sure like to know....It's giving me nightmares.