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

Hi Barbara,
I'm sort-Ed: Every attempt to remove relation on Form DE
is not allowed as long as the DBC has the p<-->>c relation.
Created a Form using Local (one child/parent) View
Can't use the local view because
A) A change to the parent is not seen on next screen (next child)
This is not really a problem as a different update Parent Screen
is provided which access' only the Parent table.
B) Multiple child changes for the same parent provide user message
about non-uniqueness of child key!!!

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

On my one-to-many screen (which has a grid) I use the DBC
and the relations hold and its very fast - Tables update buff=3.

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

No suprises here!

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

May have something here - under investigation!

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

Decided to use regular instead of candidate - I think I will delete
the Parent indexs (except for tagkeyall) and relate to
children MD,TD,and ST index' if that will work???

I'll let you know more next week - thanx Ed B