>>>>>Form parameters
>>>>>
>>>>>VFP 3.0
>>>>>Pageframe
>>>>>This grid sits on the 3rd page of the pageframe
>>>>>Grid.RecordSource = INDVS (a cursor that is tied to a particular key from the 1st page of the grid)
>>>>>Grid.RecordSourceType = 2 (Alias)
>>>>>
>>>>>
>>>>>When I look at the Grid Properties, it SAYS that the ColumnCount = 11, yet when I run the form and check that property, it says ColumnCount = 0. Wassup with that?
>>>>
>>>>Dorris, if you reset Grid.RecordSource somewhere on the way, the grid will loose the formatting and all columns. If that is the case set Grid.RecordSource ="" before the line where RecordSource gets busted.
>>>
>>>I'm not resetting the Property that I am aware of. I AM, however, recreating the cursor file....could that be what is doing this?
>>Yep, recreating the cursor will do this.
>
>well, piffle! So, that would also explain why I see the same behavior when I use a table as the RecordSource and recreate the table.....piffle, yet again!
>
>What I've got is two files that belong to two separate systems that are being updated in ONE of the systems (and having to go to an ACCESS 95 back end, no less). In one system, the primary key (VENDID) for the second system is a secondary key and may (or may not) have a 1 - many relationship with the primary key (LOCALNUM)in the first system, and I'm trying to display the multiple records in the grid so that my customer can see who is already in the files....and add more, if necessary.
>
>
>Any suggestions would be appreciated.
Instead of recreating the cursor (or table) why don't you ZAP it (or DELETE ALL) and repopulate it. This will ensure VFP does not lose the grid formating.

Another approach would be to set the grid properties programatically and that way you can reset them after recreating the cursor.