Did you remember to turn off the Ignore column when you did the Import?

Ok, I went back, and did another export, and when I imported this time there were no errors. But, nothing seems to be linked up.

I'm still doing something wrong. I did a search from the parent form, and got no child entries. I'm currently doing a search in the child, but it seems to be taking a long time.

How many Parent records were exported?
How many Parent records were imported?
Do all the fields look correct? Pay attention to the ones before and after the subform.

to start debugging lets try a simple case.

Retrieve one parent record that has a few children records.
Export it using the Set All option.
Name it something that you will remember. Leave all settings as defaults.
Open the database you are importing the record into.
Set up the import spec by clicking Set All and then turning off the ignore column.
Click Run.
Choose the export file you just made.

Does the parent record import? Do the child records import?

-Ray

Still driving me nuts, I just am not getting much computer time right now.

Ok, I have two QA4 translations.
I want to make one, a child of the other.
I have had a student, enter a 'code' field, so I can use relational linking for the two Apps.
I go into the child app, and export all data to file.
I create a copy of the child app, and then delete all data.
Going into the parent app, I created a subform. and direct it to use relational linking to the now blank child app.
I try to import into the subform,

That's as far as I've got so far, I either get no data, or very scrambled data (data in wrong LE's)

Bob,

Quote:


These above steps are unnecessary as far as I am understanding what you are doing.

When you had the student enter in the codes, are they on both the form you plan to use as a parent and the form you plan to use as a child? If they are only on one of the two forms do not follow the below steps.

Open your DB, that has both databases in it, in designer.
Redesign the Parent Form
Add a Subform element to the form
Select the form you want to display as the subform
Choose Relational linking
In Step 4 choose the correct field for both the parent and the child. Note these are the field names from the underlying database. Do not confuse these with the element names. They may be the same, they may not, double check.
Click Okay
Save
Preview
Open Search Update
Hit F10
The first parent record will display
***Does it show any child records?
If it does not show any child records, copy the value that is in the Code element and open the child form standalone in Search Update.
Paste the value that you copied from the parent form into the code element on the child form.
Hit F10
***Are any records retrieved?

-Ray

Bob,

Send me your DB and DAT files. I will have a look at them and see if anything is wrong.

-Ray

If you can, send them with more than one record, preferably around a dozen parent records and all the child records.  You may also want to try zipping them up using winzip.

-Ray

Bob,

Did you get my e-mail last night? You may want to check your spam folder if you did not. If you need me to resend it I can.

-Ray

Ray,
Lotowner is the parent form
Register is the subform
I hope to add four more subforms, all translations from QA4.
The LE that should connect them is called 'CODE'
The field name should also be 'code', but, please note that in 'lotowner', this Field was originally named 'record#', my attempt to change it to 'code' may not have stuck. (I changed it to avoid future confusion).

I need to use mass update to do that?
I can't just set the decimal format?

How would I use mass update to do that?

Obviously, you speak Sesame.
Thanks, I'll have a go tonight.

Solved the Palate colour issue. Instead of changing the palate of the subform, change the palate of the form the subform represents. That will automatically change the subform's palate.