>>Could someone explain to me which would be better... Private or Default datasessions?
>>
>>I want to be able to open multiple forms (seperate forms, not multiple instances of the same form) that may or may not share files. I also would like one user's changes to be visible to another user immediately.
>>
>>I'm thinking "Default" datasessions are what I need but I'm not sure...
>>
>>TIA
>
>It mostly depends on interface (framework) approach. Having private datasession you allow safely more direct work with data: filters, relations etc. Default datasession will generally require separation data from interface.

Whew!!! I didn't expect this many responses... Thank you all... I should also mention that the forms access the tables directly (no cursors/views). I'd say that PRIVATE is the way to go...

Although, there is one time when I need to share data. All the system options open initially with a read-only browse screen. The user presses ENTER or double-clicks to edit which displays an edit form. This form needs to be working with the record which was selected in the browse.

So I think it'll go like this... The browse screen ALWAYS uses PRIVATE DE and the edit form uses DEFAULT... Right? Seems that this will work fine...

Which was my suspicion all along...

Thanks again