>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 am a little confused...
Are you explicitly setting a relationship between the view and alias b?

A view does not create a relationship by its very existence even if the SQL that defines it joins 2 tables.

If the view is realted to the table in the dbc, and you are worried about this relationship coming over when the view is added, just remove the relationship altogether and add it the way you want it, with another alias of the table or whatever.

I have to question the reasoning for using a combination of views and relationships in the first place, though...