OK, as I see it:

- Include the other, reference table in the DE.
- Set the controlsources of the fields on the form that pertain to the ref. table to their ref table fields.
- no need for all this parameter, scatter business.
- If there is a PK-FK relationship between these, the link will show as a line. It's probable that the ref table is 1-to-m with the main form table, i.e. one of these ref records can be referred to by many of your main recs. If so, click on the link line and delete it (the permanent dbc rel. won't be destroyed - don't worry). Then effectively reverse the rel., making the ref. rec a child of the main rec, by dragging a line from the main rec's FK ID to the ref. rec's PK ID, i.e. on Artikey.
- Now, whenever you move the file pointer to a new rec in the main table, the related "look-up" rec will be located by ITS file pointer.
- You may have to refresh the form somewhere!

HTH
Let me know how you get on, huh?

Terry

>Sorry to be a pain with different threads but I have now got a form working whereby most of my controls are bound to one table. The other controls are variables passed to the form from another table which cannot be modified. Both tables have the same key field called artikey.
>
>Therefore when my program is invoked parameters are passed from one table named article and variables are stored using scatter and displayed in my form. The values are for reference and not to be modified. What I want to do is show all information from my other table named fabsum where the artikeys are the same.
>
>What is happening at the moment is the parameters are showing but the rest of the information is showing the first record from my other table. I think I need to do a set relation or something? Can anybody advise me the best way to link the 2 tables please. I have article.artikey and fabsum.artikey.