Hi guys...

The ONLY two times I use the Default datasession are whwn I am working with remote views that require a long time to load or refresh (don't want to reload each form) -or- when using a modal form to piggy back on the calling form's Private datasession.

>>>I think the benefit of the private data session greatly outweighs any negatives.
>>>
>>>HTH,
>>
>>Hello Tan,
>>
>>I simply want to inforce what Menachem just told you. The benefits of using private data sessions are immense when it comes down to "housekeeping". The only thing I couldn't figure out was to use Stored Procedures coupled with Private Data Sessions : the functions can simply not being located.
>>
>>Pat
>
>Pat,
>
>You need to do a SET PROCEDURE TO with each instance of a private datasession just like you need to open and instance of the database with each. I have a method that checks to see if it's a private datasession and then opens the database automatically so I or any other programmer on the team doesn't need to worry about it. If you dare, you can load your functions as stored procedures and when the DB is opened, they'll always be available.
>