>Good morning, David-
>
>I'd like to step back a bit and see if I understand what you want to happen. Then we can reconstruct the steps to get there. How does that sound? First, let me see if I understand what you've posted. Do please throw a sock at me if I've misread. :)
>
>You have a form that displays workorders (WOJRN), which are ordered by work order # (WOJRN.WONO).
>
>You have two comboboxes (cbo).
>One cbo is used to select work orders to view.
>The other cbo is used to pick an opcode from the opindex table.
>
>When you make a selection from the WOJRN combo you want the form to refresh to show the selected work order.
>
>When you make a selection from the WOINDEX combo you want the selected WOINDEX.OPCODE field value to be assigned to the WOJRN.OPCODE field.
>
>Before I blather on < s>, please let me know if this correct?

Yes. Though you have referred to my opindex as woindex, which may be a little confusing, since the secondary table has nothing to do with work orders...it is merely a lookup table that matches opcodes to operation descriptions (like 'Anodize', 'Electroplate'...etc.)

So for the last I'd say...when i make a selection from the OPINDEX combo I want the OPINDEX.opcode to be assigned to the wojrn.opcode AND I want the corresponding OPINDEX.DESC)to be assigned to the wojrn.opdesc field.

Last night I thought of a way to acheive my ends on the opindex lookup without using a relation. Set opindex combo controlsource to wojrn.opcode and set rowsource to opindex.opcode,desc then xfer the desc to wojrn.opdesc in the interactivechange.

If that works, I need not take more of your time now. If it doesn't, I'll respond to this message again in a few days and then, if you're still in the mood, you could help me investigate further. (The time&effort you've given so far is greatly appreciated!)

I have some unresolved issues about how relations work, but this is a more general concern that I think is better discussed in a different category.