Isn't learning a new program great fun?! Changed TransAct to Entry (checked help and it seemed ok, plus I'm using fox tables). Rebuilt my views, tables, indexes and forms and what do you know - my relation problem has fixed itself without the need for the "recno()" or "seek" plus a buggy combo box is now performing properly.

I have no idea what I've changed other than names but I'm happy for now.

Sarah

>Bret, TRANSACT may cause Sarah problems in SQL, but probably not elsewhere. Still, she'd be wise to change it.
>
>About the go RECNO('mytable') - yes, it has to be used carefully - for example it's NOT a good idea to use it after a delete if you have Set Deleted ON - you get weird results. But the SEEK could re-set your pointer in the CHILD table back to the first child record, depending on your indexes.
>
>Barbara
>
>>Since TRANSACTION is a reserved word, do you think it might be dangerous to call a table "transact"?
>>
>>Do you ever have problems with GO RECNO(something)? I often replace them with SEEK(mykeyvalue).
>>
>>>Sarah, try adding "go recno('parent')" to your INIT code, after setting the relation between parent and child. Sometimes you have to tell VFP that it's time to activate the relation, and the easiest way is to "move" the record pointer. That's why the relation works after and edit or add.