Not possible to add external data source

[MogensBrun]

From a local FileMaker file ("local.fp7") it is - of course - possible to relate to tables in a remote FileMaker file ("remote.fp7") through establishing the latter as an External Data Source in the first.

However, the reverse is not true - at least to my experience. From the FMP 10 Help file "Creating file paths" description of relative file paths I would expect that something like "file:./local.fp7" would work as External Data source in "remote.fp7", if "local.fp7" is stored in the FileMaker application folder because "If the current database is opened remotely, the path starts from the local FileMaker Pro directory" (citation).

But it doesn't work. So there seems to be no way for FileMaker 10 (or below) to establish a local file as data source for a remote file. Any suggestions?

[David Jondreau]

I don't see how that would work.

An data source's needs to be defined relative to the served file. How would the database know which local file to use? Or is it supposed to use a separate local file for each user?

You can define an external data source that is the local machine. But you've got to have a static IP.

[MogensBrun]

The "local.fp7" and the "remote.fp7" both belongs to the same solution. The "local.fp7" contains the user interface and no business data - only session data - while the "remote.fp7" has all the business data stored. Each user has his own copy of "local.fp7".

I would like the "remote.fp7" to have access to some session data from each users "local.fp7". As mentioned, the Help file explains, that a remotely opened file will use the local FileMaker Pro directory as strarting point for a relative file path. So in theory one should be able to relate from "remote.fp7" to "local.fp7" using a relative file path. However, that doesn't work - at least for me.

[Søren Dyhr]

However, that doesn't work - at least for me.

I would be even more surprised if it did, the referential ties are one thing but the appearance of the tables as TO's in the other should be voluntary... and entirely up to the developer.

--sd

[Vaughan]

Once the local file has opened the remote file, the remote file can access data from the local file during the session.

[Søren Dyhr]

I don't get it, scripts running in the remote can access all fields - Vaughan??

--sd

[Vaughan]

Put a TO of the external file in the local file, make a layout with the TO, and you can access the local file from the remote file.

Like I originally said, this can only happen while the local file is open.

[Søren Dyhr]

Put a TO of the external file in the local file

Ah! What I thought ... just puzzled with the wording made!

--sd

[MogensBrun]

It will work if you are the only user of a solution.

However, if "local.fp7" is the user interface (in a Separation Model) and there are a number of users, you cannot be sure that TOs in "remotel.fp7" to tables in "local.fp7" will work. If a user has renamed his harddisk, or any of the other folders in which "local.fp7" is stored, the TO in "remote.fp7" will break.

It might work if it was possible to set up a relative reference from "remote.fp7" to a "local.fp7". Then you should only place the "local.fp7" or an alias to "local.fp7" in FileMakers application folder - or relative to this folder.

As mentioned, the FileMaker Help file explains relative file references, but they don't seem to work from "remote.fp7" to "local.fp7".

So therefore my conclusion: In a separation model it is not possible to access data in "local.fp7" from "remote.fp7" - unless you are the only user.

[aholtzapfel]

You may be able too. I have set-up External Data Sources in remote files that point to local files but you must be consistant about where the file is and use an absolute path. (use a folder path on the local computers that is useable by all users.) I have not used these sources in relationships and cannot predict how they might react in a multiuser enviroment. Local Sources can be used to open files run scripts. Key is that the local file(s) must be at the same absolute path for everyone using the datasource.(one file for each computer and must exist.)

There are so many ways that this could go wrong so please procede with caution.