Are you running this on a local machine, or is it located on a server somewhere?
Here are my guesses:
1. The cursor is being recreated somehow in your app. If you have a "SELECT * from myTable into myCursor" somewhere in your app - well every time you do that it will mess up your grids - the recordsource/control sources all have to be reset in code.
2. The cursor is actually being created on some other hard-drive that's networked, and the network connection is flakey. If you .exe is on a server and you run it on your local machine - I dunno but maybe the temp tables that cursors creates are being put on a networked drive somehow?
One thing I would try would be to use a local view instead of a cursor and see if that works.
>I'm having this problem with occasionally disappearing grids.
>
>Each of the three grids for which this is happening are on different pages of a pageframe. (There are a few other pages as well, but they are not relevant.). They are all based on the same class (a sub-class of my base grid class)
>
>The columns for each grid, as well as their RecordSources, are created in the Activate for the page they are on (only the first time, though).
>
>What I am getting, some of the time, is that the grid appears, has all the columns I am expecting to see, but no rows appear. I can tell that the recordsource (a cursor) exists, has records, does not have a filter, and the record pointer is on the first record.
>
>MOST of the time, when I bring up this form, the grids appear as desired. But some of the time (20% ??), the grids are blank. When they are, closing the form and re-opening it causes them to display properly. (When any of the grids are blank, they are all blank --)
>
>I have used the base grid class which creates the recordsource and add columns a zillion times, throughout all my applications. (Most of which are very heavily grid-reliant). I have not seen this behavior before.
>
>I cannot even begin to guess what may be happening here. Any thoughts?
ICQ 10556 (ya), 254117