Ok, I sent you the files, with data for just my family name.
If you need to make stuff up for more records, go for it.

No, I didn't get it, did you send it to my work email?

That's the one that is in my profile. If that's the case, I won't have it yet, I've been out of the office for a bit.

Bob,

I believe I see what your problem is. On your parent form Code is Text and on your subform Code is also text.

In your parent datbase you have the code values of
3926.000000
3977.000000
4023.000000

In your child database you have code values of
1294
3977
4023

Since the code fields are text 3977.000000 is not the same as 3977. If you mass update your parent form to remove the decimal place and the zeros, then the linking will work. Let me know if you need me to send back the copy I have working here.

-Ray

Yes you will need to use a Mass Update unless someone wants to do it by hand.

You can't set the decimal format as both of the elements are bound to text fields not number fields. It looks as if the element on the parent form was once bound to a number field hence the multiple zeroes.

A mass update that can do this is

Var vCode as Int

vCode = @ToNumber(Code)
Code = @Str(vCode) 

The reason to use an Int variable is because they can not store decimal places, which eliminates the zeros.

-Ray

Things are going very well, I have brought in two subforms so far, no need for the import/export routine I was doing before. Real easy, takes maybe five minutes.
Thanks very much Ray

One thing though, the pallate colour doesn't reconcile from designer to sesame. It shows in the preview, but won't come across.