>>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...

Hello Erik

I need to have a form where A is the parent of B and I will be updating data on A. I also would like to use a local view that is defined as joining A and C in order to get the required data. My question is this, since I set relation between A and B and have buffering set on A (row), and I use the view. Will the view use the A that is already opened to do its query and thus move the pointer on A causing my unsaved data to be save (as moving off the record in row buffering does a tableupdate automatically) or will the view not disturb my already opened A?

I know that is a mouth full, but I hope I cleared the question up.