Hi all -

Please forgive my ignorance but I want to import to one table in a master file from the same table in a copy of that file - and I am having problems.

I go File > Import... and double click on the file I want to import from. This brings up the Import Field Mapping dialogue.

In the Source I select the table I want to import from. However, in the Target I find that the table I want to import to is "grayed out" and cannot be selected.

I can of course select "New Table" and that creates a new table (with the data I want to import in it)... but then I cannot get the data across from the new table to the old (master) table... (same problem as above).

Any suggestions?

What am I doing wrong?

Thank you.

Something clearly must be wrong here, you try to import into a copy and that copy is the frontmost solution?

The graying out seems to suggest that your focus file is the source?

--sd

However, in the Target I find that the table I want to import to is "grayed out" and cannot be selected.

If your table is grayed out when you pop open the target table list then it might suggest that your layout you are attempting to import into is not based upon the same table occurrence.

Oh... LaRetta is right! I need to be in a layout based on the table I am attempting to import into before I initiate the import procedure (duh ...how is it that sometimes the most simple thing will trip us up?).

However, now I can foresee another problem arising from this... I have a portal based on a table but no layout directly representing that table - yet I need to import into it. Does that mean I will have to create a layout specifically for that purpose? Then do I need all the fields on that layout or can I get away with just one (just to make an active layout for FM to register its presence)? I'll experiment.

Thanks for the replies Soren and LaRetta.

Much appreciated!

Rramjet.

I have a portal based on a table but no layout directly representing that table - yet I need to import into it.

You should always have at least one layout for every table otherwise you can't do anything with the tables. It doesn't have to be that exact same table occurrence; table occurrences are generic when it comes to creating new records, deleting, importing etc. (meaning you can run that script no matter the occurrence) so if you have a layout based upon same table but another occurrence, you can import into that one instead. This also applies to GTRR (you can go to related records of one table occurrence but display the found set in a different table occurrence; if same table).

Then do I need all the fields on that layout or can I get away with just one (just to make an active layout for FM to register its presence)?

You can import into a table without any fields present at all (FM knows because it looks at the table occurrence tied to the layout itself). But it is always good to have one Developer layout (usually table view). It will also come in handy when viewing or modifying data (when browse is restricted on other layouts), when debugging, copying all records and such.

Edited April 27, 201015 yr by Guest