>If I already have table A and B open where a relation is set the A is related to B (parent child) and I open a view, USE view_B_C. This view has B as the parent to C in a join. Will the view open another instance of B to do its work or will it use the B that is already and thus move B's record pointer. If this is the case is there a way to tell a view (created through the DBC) to not use existing tables?
>
>TIA

I believe that the view does use an alternate work area for the "B" table to be opened for the view and will not cause problems with the A/B relationship set up previously.