Instead of closing the cursor, ZAP it. After the next SQL statement is executed, append result into the cursor.

>
>This is my problem.
>
>I have a form and on this form sits a grid with multiple columns. When the form initially opens the grid is empty of data, as they should be.
>
>When a search routine is invoked, a SQL statement hits a SQL Server table and populates the grid from the cursor. The user can then clear the screen which in turn empties the grid of the data as well as emptying the other screen objects.
>
>The problem is when the clear screen is issued I close the cursor that is responsible for populating the grid, and this causes the grid to lose its layout properties, methods and other related items. I can reformat the grid for the next SQL statement but it's a chore and I'm not sure how to reload event statements when they are lost.
>
>Anyone run into this issue before?
>
>Thanks for your help.
>
>Jerry