>"Heaven forbid" only because of references I've here in UT apparently disparaging them. I have a number of applications which are entirely dependent on grids, and can't imagine any other way of presenting the information to my users. (and I don't think it merely reflects a lack of imagination on my part.)

That's just one wayward soul. Please don't mistake me for him. ;)

>
>>My recommendation is that continue to use private datasessions.
>>Why "heaven forbid" for grids? :) I wouldn't forbid till they create the next closest powerfull object.
>>Cetin
>>
>>>You might consider putting that data into cursors and having the forms use the default data session. You might also consider having that object instantiated within the data session of the first form and have other forms called by buttons on the first form. Such called forms can adopt the data session of the first form.
>>>
>>>Have tried for some time to avoid having forms share data sessions. Most of my forms create cursors which are then used in grids (yes, heaven forbid, my apps are based on grids, but they're the example of when using grids are appropriate). Sharing a single data sessions then causes major headaches with replication of cursor names.
>>>
>>>Thanks for the suggestion in any case,
>>>
>>>Jim
>>>
>>>