>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

Hi, Ed. I appreciate your frustration. I've gone the #@*#^ route on grids more than once.

Try this approach:

1. REMOVE the parent/child relation in the data environment, and do not set it in code. (It's OK to leave it in the DBC, just not on this form)

2. Use the Grid data properties to show which tables are linked (linkmaster, relationalexpr, etc. This lets the grid handle ALL the linking.

3. Pop up your debugger, and keep a watch on your parent record and your child records as you move around and make updates.

4. Are you issuing the tableupdate to the correct table? (Sounds silly, but your SELECTed table may not be the one you think)

5. Also, are you SURE you have the correct settings for your candidate and primary indexes. Candidate indexes hide in the background and give your kind of errors.

HTH
Barbara