I assume you are using vs. 7 or greater ...
- There is no need to ever go to another file. You can work with ANY .fp7 file right within your existing file. Create an External Data Source to the other file so it appears in your graph (File > External Data Source). Then create a layout to any of the tables from that file right within your working file and script going to those layouts instead of jumping between files.
- Usually, the only time it is necessary to use another file is when you are separating UI from Data otherwise all tables can be within the same file.
- Copy/paste is rarely used ... instead it is best to use Set Field because copy destroys the User clipboard contents and paste requires that the field be on the layout to work. This can be a problem because 1) you may not need the field on the layout, 2) you may forget and remove the field from the layout and 3) it means you can't set related fields from a layout.
- When you are attempting to set multiple fields from one table to another, it indicates that you are missing key concepts regarding relational theory. Usually it means that you do not understand how to use Keys (primary and foreign keys) to relate your data so duplicating the data (redundancy) becomes unnecessary.
We cannot properly answer your questions without knowing specifics. We need to know the purpose and context of the tables/files involved, i.e. is it an Invoice file and and a LineItems file, set up as a one-to-many? Is it Customers? It is best if you can provide a link to your file for review but, at minimum, consider seriously the bullets above and then provide detailed description of what you want to accomplish and not how you think it should be accomplished.
We can help you once we get you on the right track and once we have clear understanding on what you wish to do. :^)
Thanks, sorry about the lack of clarity in my explanation.. I realize how it would have been impossible to answer without the specifics of what I was trying to do. As you guessed, I basically wasn't using some core relational database theories, but the advice you offered got me on the right track. The solution I'm working on (in FMP 11) uses multiple files both to separate records from the UI and also to restrict access to certain records.