>>>>I am using a form (Private Data Session) with a grid that is populated from an
>>>>SQL select to a cursor called DailySked .. It works wonderful except for one
>>>>thing. If the form is active on one workstation and called again from a second
>>>>workstation with a different data set, both forms are refreshed with the second
>>>>workstation's query. This is good in some situations, but not really what I am after.
>>>>Is a Private Data Session not supposed to be Private ? I also thought temporary
>>>>cursors were local to the worksataion ??
>>>
>>>Private data session is application specific. I mean, the table involved, the record pointers, etc. are private versus other forms in the same application.
>>>
>>>I have some difficulties to understand what can make a cursor to be updated from another workstation operation.
>>>
>>>BTW, is that really a cursor or a view?
>>
>>No I am not using views ...
>>I'll try to explain more clearly..
>>
>>I have a table that has a fixed x,y count. When my form is run it fills the cells of
>>this table with data. (basically Daily schedules) The original grid on this form was
>>bound to this table but I noticed that when the form was run on another workstation it
>>repopulated the table and because the grid was bound to the table it got refreshed on
>>all the workstations that had that form active. (This is not what I wanted) So I figured
>>I could populate the table as before (in the form.init) and then do an SQL select into
>>a cursor to give individual workstations their own snap shot of the table. The grid
>>recordsource is an SQL select all on the table into a cursor called Dailysked. The
>>recordsourcetype is SQL and the grid columns are bound to DailySked.field(s) (the cursor).
>>The logic here is that the cursors would exist on the workstations and be independant
>>of one another. This does not seem to be the case. I also have a config.fpw that sets
>>the workspace to the local drives.
>>
>>Any thoughts ??
>
>You should use cursor alias as Grid.RecordSource (RecordSourceType=1), and this should resolve your problem.

Nope .. If I use grid.recordsource.alias then the grid is not populated at all.