Import between 2 Filemaker solutions

[sedek]

I have 2 Filemaker solutions. Each of them will be a separate runtime.

Solution One contains a table named 'Job'

Solution Two also contains a table named 'Job'

I wrote a script to have solution Two delete all data from its own table 'Job' and replace it with the content of solution One wich is always current.

To make it simple, both tables have the same name 'Job' and 6 fields with exactly the same names also. (So they are identical by name and structure)

This is where it gets tricky:

I cannot assign paths in the import script because I cannot know in advance where the users will place either solutions. Most common scenario is 2 different computers inside a network.

Then when the script triggers, it warns solution One can't be found and opens a window to locate it. This part is easy to handle for users.

But what happens next is that the script goes on from there and always does its mapping with the wrong source fields (i.e. another table) so we end up with garbage.

The only way to make it work is by unchecking 'perform without dialog' and have the user align source fields with target fields, but users cannot handle this part.

Is there a way around this?

If no solution arises, I'll have to merge the 2 solutions in one and make a single runtime. However this a huge work and I will lose the flexibility to allow 2 different users to work on my application.

[bcooney]

Perhaps this technique will help.

[ron G]

I use 360Works ScriptMaster SelectFile() plugin.

It is 'free' and it allows the user to select the file desired and then you can simply produce the resulting path.

However, be aware, if you are running your app in OSX, you MUST use Allow User Abort ON. Otherwise you will get the 'spinning beach ball'.

By the way you may want to ignore the parts of the script dealing with finding the digital portion of the filename. It is a part of the logic that determines which files I use with Import.