importing disaster??

[livvie]

I recently updated two related databases and created clones of them to import current data.I did have to re-establish the relationships. After importing data into the two files(i.e. clones), the master file which has a portal set up on the main layout looked okay until I tried to create a new record. The portal should come up blank for data to be entered but it seems to already have data (it seems existing data as the key is an existing one) in the top half of the portal which is where master data is input. The lower half which will normally display data from the related file still stays blank as it is supposed to. Can anyone please help? Have I completely missed the plot or is cloning and importing data into clones not as straight forward as I thought?

[CobaltSky]

Sounds like the problem is that you opened and ran the files with the names (or at least one of them) no longer exactly matching those that were defined as the basis of various dependencies - most notably the relationships. This results in broken links in your databases, which is why you'd have had to re-define the relationships.

From what you've said, the subsequesnt problem almost certainly results from you changing one of the keys at the time you re-set-up the relationships. I'd suggest that if you can, you re-open the original filfes and take careful note of the fields that were used on both sides of each relationship (and the other relationship settings). That's at least a good place to start trying to trace the cause (and therefore the solution) to your problem.

[livvie]

Thanks, I'll try that out.

[livvie]

I think I spotted the cause of my dilemma, the key on the master file had an auto serial option set up on it and all I needed to do was to reset that to the next available record to be incremented by 1 as was required. The next value was set to that of an existing record. Thanks for looking into this for me.

[CobaltSky]

Yes, that would account for it. You didn't mention serial numbers being the basis of your key field, but I still probably should have thought of that from your description.

Anyway, sounds like you're back on track now, which is good news!