Dear Sergey,

From the description of the your problem, I've reconstructed the situation. From the Command Window :-

Try this to break the 1-M :-

SET RELATION TO && (lcParent) must be SELECTed
SET ORDER TO 0 IN (lcChild)
_SCREEN.Forms(2).REFRESH && Forms(2) is Child


Try this to re-establish the 1-M :-

SET ORDER TO &lcOrd IN (lcChild)
SET RELATION TO &lcOrd INTO (lcChild)
_SCREEN.Forms(2).REFRESH

It works (VFP5.0, SP3) on this side of the globe (.my).
Kenneth (mailto:kensoft@tm.net.my)


>VFP 5.0.
>Question about SET RELATION in a grid. So, let's take
>two tables - PARENT and CHILD. Let's make 2 simple forms -
>one form with a grid for PARENT, another form with a grid
>for CHILD. Both forms are modeless and running in Default
>Data Session. No DataEnvironment assigned to forms - all
>table openings and relations are created from outside -
>from Command Window, for instance.
>Now, creating relation from PARENT to CHILD with
>SET RELATION TO SomeKey INTO child
>All fine - while moving a pointer in PARENT, I see only
>the selected records in CHILD.
>When I issue SET RELATION TO without parameters in
>PARENT area, I expect that _all_ records must appear in
>CHILD grid. Oops, they are still few as if the relation
>is still active. Let's try SET RELATION OFF or USE in
>PARENT area. Not much better - records in CHILD grid are
>still "filtered". Refresh method for CHILD form does not
>fix a problem.
>Record pointer in a CHILD grid is movable, we can
>position it on any record by GO TO, but only previously
>selected records are visible, until we re-create a form
>or a grid :(((
>So,how can I restore a pre-relation view in a grid
>without rebuilding it ?
>
>Sergey
>reware@cafe.redcom.ru