Copy is rarely the best script step to use to move data from one table to another.
Is "Flue Test" a FileMaker database file?
If so, why is it a separate file? Why not define a table for flue test data in your Medical Records File?
Yes. "Flue Test" is another filemaker pro Database. The reason why is a separately file, it is because the database "PersonKjema" (main) has been used since 2009 to compute medical records and it contains hundreds of fields and records already. "Flue-Test" as other new Tes or flies, are Medical R&D for statistics and are used only with some of the patients and used from this year; therefore it was decided to have it as a different file.
"Personkjema" File contains also some other test-files for exmaple "OLD flue-Test" (filamakerpro) that was used for patients in 2011 ofr example, and there those buttons perfoms and scrip similar to what I want to do. By inspecting the buttons , tables, fields and relationships I have been managing to update functionality for the new tests we want to add, and Copy function has been used there. It may be that I am missing somthing when trying to leanr by exploring old scripts.
it contains hundreds of fields and records already.
Which does not mean that you can't add an additional table to the file. You would not add these fields/records to the existing table.
Using a separate file complicates your design.
What version of FileMaker are you currently using?
And please note that even with the table in a different file, you can still define a relationship between the table in one file and the table in another file by setting up an external data source reference.