I have an accounting solution where a script imports records from a
table in the same file.

If the file is called myfile.fp7. In the import script step, the file
reference file:myfile.fp7 is stored.

Clients may want to change the file. But if they do, the script will
look for the old file name.

Telling the clients not to change the file name is a no go, it must be
possible to work with several copies of the solution (accounts of more
than one client - my client's clients, that is).

Is there a way to tell Filemaker that the table with the records always
resides in the same file?

I could tell the clients they'll have to change the script if the change
the filename, of course. Or export to a text file and then re-import.
-- 
http://clk.ch

Christoph Kaufmann wrote on (10/4/2005):

>I have an accounting solution where a script imports records from a
>table in the same file.
>
>If the file is called myfile.fp7. In the import script step, the file
>reference file:myfile.fp7 is stored.
>
>Clients may want to change the file. But if they do, the script will
>look for the old file name.
>
>Telling the clients not to change the file name is a no go, it must be
>possible to work with several copies of the solution (accounts of more
>than one client - my client's clients, that is).
>
>Is there a way to tell Filemaker that the table with the records always
>resides in the same file?
>
>I could tell the clients they'll have to change the script if the change
>the filename, of course. Or export to a text file and then re-import.

Someone else may have a more elegant snawer, but here's my quick and dirty 
test:

Set Error Capture On

Import

If Get ( LastError ) = 100

Open Define File References

Perform Script [ ThisScript ]

End If

Tell your clients they can change the file name, but if they do, they will 
see that Define File Reference dialog and how to deal with it. Maybe the 
won't bother.

Matt

--