>>>I would enter a change to Parent--Child
>>>Go to the Next record
>>>Attempt to edit either
>>>1) the second Child of the same parent
>>>or 2) the Parent
>>>and the system would Lock up requiring a PC reboot!
>>>I got rid of the View - no more PC Lock up !
>>>Does that give a hint of what I am doing Wrong?

>>1. Were your views 'updateable' (and are you sure you had all the right items >>checked off, including the "Send SQL Updates" checkbox?)
>>2. Did you have a tableupdate() command before changing records in the view?
>>3. Are you using the RI to enter your primary keys?

I alone handle Parental Primary Keys (the key-values are stored in secret table)

>>If you're using filtered records in a grid, check out the Foxpro Advisor article on this (Sept. 97).
Great Article - will implement later!

I removed all filtered keys:
now (Index-connect) Parent.tagkey <-->> Child.tagkeyall only relation
Created View conditions-
View all fields, Send SQL Updates
Key fields auto-made Parent.tagkey -- Child.tagkey (Field-connect)
Made all editable except Parent.Tagkey
SQL W/ key and modified fields
SQL Update
No Grouping, No Having, Order By Child.Tagkey field

Unusable . . .
1) For proper reflection of Parent field Edit (where multi-child),
I must requery.
2) Change Parent, Do TableUpdate(),
Change next Row same parent diff child get:
UPDATE CONFLICT use TableUpdate() with lForce param to commit
or TableRevert() to Roll back ... ((ok lets look at child))
3) Change a Child Field, Change another Child of Same Parent get:
WARNING! The key defined by the keyfield property for table ...
is not Unique.

%^^&#%^ WHO CARES - Pardon my frustration.

From that I believe it is ignoring the Relation set in the DBC!
Are we having fun yet? Thanx :~| Ed B