I am building a solution that is cross platform (Mac OS X, Mac OS 9, and Windows). In fact, this is one of the primary reasons for doing this in FileMaker!

I have scripts for upgrading solutions. The upgrade scripts record an import from another parallel folder. I instruct the user to rename the old folder and then run the script. The old folder is found and the data copied to the new database.

I do my work on OS X and this worked great, even after building the solution with a different extension.

However, when I transfer this application to a Windows solution, the import process fails, saying that it can't find the other database.

I examined the binary contents of the database and discovered that sure enough the relative path in a Macintosh format was saved in the database. It appears that the Developer Tool is smart enough to change the file name but not the path!!!

Is there a solution to this that doesn't require recording different information for Windows and Macintosh. Suggestions on how to make the paths look the same or bug fixes that I don't know about would be great. For that matter any suggestions would be helpful.

Thanks for the suggestions,

...Duane

Hello Duane,

Within your import script, when you specify the data source (file) for the import you will be presented with a file reference dialog which exhorts you to provide a 'File Path List (in search order)'.

I suggest that you list an explicit path for each platform in the File Path List. That way, if the first one is not found (depending on the platform) FileMaker will search for the second and the user will be none the wiser.

Thanks for the tip. Unfortunately I am on FMP6. I think that must be the bug fix that's in FMP7.

I don't see such a dialog. If it's supposed to be in 6 then, I'll need some additional details. I'm not seeing anything like you describe.

Begging your pardon, Duane. I overlooked to check what version you were using. The dialog I mentioned is a new feature in v7.

In v6, your best bet would be to create two separate single-step scripts, each configured to perform the import correctly on one plartform. Then set up your main script to dynamically call the appropriate import subscript depending on what the current platform is. Eg:

If ["Abs(Status(CurrentPlatform)) = 1"]

Perform Scriupt [sub-scripts, "Import (Mac)"]

Else

Perform Scriupt [sub-scripts, "Import (Win)"]

End If

It's a little clunky, but it will get you there.

Thanks for the confirmation. That's where I was headed. I think this will work out fine. A little tedious to setup (6 files), but it should work.

It's going to be a while before we get to 7, but I am looking forward to it.