>I have the search in the form. It's a private datasession form. Any form that needs that cursor is called from that form. The called form adopts the datasessionid of the calling form very early. The called form does not open any cursors already open. It leaves anything it opened open in the calling form. That is very fast as there is no passing or processing of tables/cursors/XML.
>
>I take it that the browseable search form you use fires the actual data entry form and is passed the search form's datasessionid? So, like if user choose Customers, it fires this browseable search form (of course with buttons for New, Edit...).. also for Products etc..?

No. I use a pageframe. The grid is on page 1 with search utility. The second and other pages are for data entry. One form. Why make the user do the hokey-pokey dance across multiple forms?

>
>Thanks
>Dennis
>
>
>
>>>TC,
>>>
>>>That is what I typically do. Many forms will have a grid for browsing and a data entry section on the same form, or the main form will only have the fields for displaying editing and the toolbar. When you click search you enter the values you wish to search on and then a separate form with a "result" grid on it pops up with the result. You select the record you wish to view on the main form and the browseable grid form goes away. However, that same result set is used in the main form so you can step through the records using the toolbar. The nice thing about that is you can use the same result grid form from any form that calls it - you just pass the result set to it or you pass the query and dynamically display the columns.
>>>
>>>How did you pass the result set from the form with the browseable grid back to the 'main form'? Does the browseable grid form have a Default Data Session? Can cursors be passed as parameters to a form?
>>>
>>>Dennis