Import between 2 runtime solutions

[sedek]

I have created 2 runtime solutions.

None of them have admin rights. However, they both are accessed individually with the same user/password combination.

I have a script that gets runtime TWO to import data from 7 or 8 different tables located in runtime ONE.

Is it possible to enter user/password only once when the script runs?

Actually, it asks user/password for every single table accessed by the script. This is very unelegant.

[IdealData]

You need to be able to use the "Open File" script step, however with a runtime solution this is restricted to the files that were included at the time of binding, and it will not let open the other runtime file.

If this is an attempt to provide an upgrade path then you could build your runtime with

DataFile.fp7

DataFile Copy.fp7

where "DataFile Copy" is what it suggests - a copy of "DataFile", then you will be free to open "DataFile Copy" before any imports are attempted and avoid the authentication on each table import.

Other than this, export from RUNTIME1 as csv or xls and import into RUNTIME2, no passwords required for this either.

[sedek]

When I create a runtime, I can add another .FP7 as secondary. But what is the use of this, since the runtime will not open it later?

As for a copy of datafile, I don't see any change. Still a request for password.

Seems that 2 runtimes will never exchange data automatically without asking the end user for a password on each table opened. Maybe I'm just asking too much for the small amount of experience I have with Filemaker.

You need to be able to use the "Open File" script step, however with a runtime solution this is restricted to the files that were included at the time of binding, and it will not let open the other runtime file.

If this is an attempt to provide an upgrade path then you could build your runtime with

DataFile.fp7

DataFile Copy.fp7

where "DataFile Copy" is what it suggests - a copy of "DataFile", then you will be free to open "DataFile Copy" before any imports are attempted and avoid the authentication on each table import.

Other than this, export from RUNTIME1 as csv or xls and import into RUNTIME2, no passwords required for this either.

[Vaughan]

Maybe I'm just asking too much for the small amount of experience I have with Filemaker

It's worth pointing out that you are working with runtimes. FMI has chosen to "restrict" runtime functionality in several ways, including the ability to share and exchange data.

If you need the "extra" functionality then use the FMP client, not the runtime.

[IdealData]

Sounds like your situation is the files are from 2 SEPARATE runtime bindings, in which case the Open File step cannot work. I was proposing a solution that provides an ability to use the COPY database as a resource within the runtime for 2 possible options:

1. Restore to a previous backup using FM Scripting

2. Upgrade the primary file, whilst using the COPY file to hold the current data, then import the data from the COPY

[sedek]

Thank you all for your help.

I found out that by asking the .exe to open the second .USR file ''manually'' it works !

The downside is that both files are opened in two separate windows in the same global exec, but at least it all works without more input from the end user.

As for getting more flexibility, then the user will have to invest a little bit more, but my point is to get his attention in the first place.

I will be putting the demo online in the coming weeks. It is a cost accounting and production management application.

Message to Vaughan: I never answered you on another post. I did change all the fields names to avoid reverse engineering on my runtime. That was truly helpful. Thanks.