>You could create a property in the primary form, say NbRef, and initialize it at zero. When each form using the primary's form datasession is created, increment the property by one. When they are released, decrement it.
>
>In the QueryUnload() of the primary form, if NbRef > 0, issue a NODEFAULT.
>
>BTW, why are you using the same datasession?

Sylvain,

I appreciate your response. It should work for me. I guess I should 'bite the bullet' and download SP3 to check out Arnon's response also.

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. 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). 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.


>
>>The user usually has a primary pageframe displayed because it contains client information, telephone log, shipping,etc. This form is set to private datasession.
>>
>>The user can select other forms: Work In Progress, invoices, payments, etc. If the primary form is open, the other form opens using primary's datasession...if not, it uses default.
>>
>>The problem is, the user accidently closing the primary form when its datasession is being used by a second form.
>>
>>How can I prevent this from happening?