How to create scripts in another file?

[summergirl]

I am releasing a new version of an existing FM Developer 5.5 solution. I want to create a simple FM file that will:

-show all records in each of the 3 old version data files;

-create a compressed copy of each old data file; and

-import records from the 3 compressed copies into the corresponding 3 new version files.

My hangup is described in this FileMaker Help topic:

"Open" script opens the specified file or lets the user select a file to open. [color:"red"] Script steps after Open execute in the file that contains the script, not the file opened by the script.

Is there an easy way to create a simple file with script directions to do the 3 tasks shown above? I tried to write a script in Simple File that would Open Old Db1, then Save a Copy. The result is exactly as described in the Help topic - Old Db1 opened, then a copy of Simple File was created... not what I'm looking for!

Some of my customers have a very hard time with importing, so I'm trying to automate.

All suggestions welcome. Thanks!

[summergirl]

I am releasing a new version of an existing FM Developer 5.5 solution. I want to create a simple FM file that will:

-show all records in each of the 3 old version data files;

-create a compressed copy of each old data file; and

-import records from the 3 compressed copies into the corresponding 3 new version files.

My hangup is described in this FileMaker Help topic:

"Open" script opens the specified file or lets the user select a file to open. [color:"red"] Script steps after Open execute in the file that contains the script, not the file opened by the script.

Is there an easy way to create a simple file with script directions to do the 3 tasks shown above? I tried to write a script in Simple File that would Open Old Db1, then Save a Copy. The result is exactly as described in the Help topic - Old Db1 opened, then a copy of Simple File was created... not what I'm looking for!

Some of my customers have a very hard time with importing, so I'm trying to automate.

All suggestions welcome. Thanks!

[summergirl]

I am releasing a new version of an existing FM Developer 5.5 solution. I want to create a simple FM file that will:

-show all records in each of the 3 old version data files;

-create a compressed copy of each old data file; and

-import records from the 3 compressed copies into the corresponding 3 new version files.

My hangup is described in this FileMaker Help topic:

"Open" script opens the specified file or lets the user select a file to open. [color:"red"] Script steps after Open execute in the file that contains the script, not the file opened by the script.

Is there an easy way to create a simple file with script directions to do the 3 tasks shown above? I tried to write a script in Simple File that would Open Old Db1, then Save a Copy. The result is exactly as described in the Help topic - Old Db1 opened, then a copy of Simple File was created... not what I'm looking for!

Some of my customers have a very hard time with importing, so I'm trying to automate.

All suggestions welcome. Thanks!

[NYPoke]

Step One & Step Three should be easy:

- Create Relationships, in Simple File, to all three other files.

- Create Portals for each Relationship

- Loop through each of the 3 Portals

- Create a Record in Simple File for each Portal entry & transfer the data

Step Two really needs a script in each of the Old Files, which you would call as an External Script from Simple File. Are you compressing them to save space, or to keep them from running the old app by accident?

If you really don't need to compress, you could use an external script of some sort (AppleScript or something on MS) to rename the files to non FileMaker Extensions. Something to keep them from reusing them by accident. Rename & Write Protect.

[NYPoke]

Step One & Step Three should be easy:

- Create Relationships, in Simple File, to all three other files.

- Create Portals for each Relationship

- Loop through each of the 3 Portals

- Create a Record in Simple File for each Portal entry & transfer the data

Step Two really needs a script in each of the Old Files, which you would call as an External Script from Simple File. Are you compressing them to save space, or to keep them from running the old app by accident?

If you really don't need to compress, you could use an external script of some sort (AppleScript or something on MS) to rename the files to non FileMaker Extensions. Something to keep them from reusing them by accident. Rename & Write Protect.

[NYPoke]

Step One & Step Three should be easy:

- Create Relationships, in Simple File, to all three other files.

- Create Portals for each Relationship

- Loop through each of the 3 Portals

- Create a Record in Simple File for each Portal entry & transfer the data

Step Two really needs a script in each of the Old Files, which you would call as an External Script from Simple File. Are you compressing them to save space, or to keep them from running the old app by accident?

If you really don't need to compress, you could use an external script of some sort (AppleScript or something on MS) to rename the files to non FileMaker Extensions. Something to keep them from reusing them by accident. Rename & Write Protect.

[summergirl]

Thanks for the suggestion.

Do I understand correctly that there is no way to write a script in Simple File that will CREATE the "Save a Copy As" script in each of the Old Files?

[summergirl]

Thanks for the suggestion.

Do I understand correctly that there is no way to write a script in Simple File that will CREATE the "Save a Copy As" script in each of the Old Files?

[summergirl]

Thanks for the suggestion.

Do I understand correctly that there is no way to write a script in Simple File that will CREATE the "Save a Copy As" script in each of the Old Files?

[NYPoke]

Not that I am aware of. I'ld be interested if somebody knows how to do it. One of those irritating things about FileMaker.

One suggestion though: Put the script in your new version, hidden & password protected, then you can use it in future releases.

[NYPoke]

Not that I am aware of. I'ld be interested if somebody knows how to do it. One of those irritating things about FileMaker.

One suggestion though: Put the script in your new version, hidden & password protected, then you can use it in future releases.

[NYPoke]

Not that I am aware of. I'ld be interested if somebody knows how to do it. One of those irritating things about FileMaker.

One suggestion though: Put the script in your new version, hidden & password protected, then you can use it in future releases.

[summergirl]

Ah, just as I suspected. I guess the FM folks overestimated my ability to see into the future when creating scripts I MIGHT need later on.

Thanks again for your ideas and quick reply.

[summergirl]

Ah, just as I suspected. I guess the FM folks overestimated my ability to see into the future when creating scripts I MIGHT need later on.

Thanks again for your ideas and quick reply.

[summergirl]

Ah, just as I suspected. I guess the FM folks overestimated my ability to see into the future when creating scripts I MIGHT need later on.

Thanks again for your ideas and quick reply.