Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 6805 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I have a collection of general FileMaker files that I combine to create a specific solution, with a master Welcome file with "links" to the other files. The "links" actually perform a common Activate script in each of the subordinate files.

A have been customizing the Welcome file for each specific solution. I thought I could avoid this customization by having the Welcome file perform the Activate on all possible subordinate files by having a single Proxy file stand in for any missing files.

Each File Reference definition lists the actual file and the proxy:

file:ABC.fp7

file:Proxy.fp7

This almost works. Welcome can perform the Activate script in ABC, DEF, GHI, .... When one of the files is missing, Proxy.fp7 gets called.

However, once Proxy.fp7 has been called, all subsequent file activations go to the Proxy even if the actual file exists. That is, if DEF.fp7 doesn't exist, Proxy.fp7 is called. Then, even though GHI.fp7 exists, activating the GHI file reference goes to Proxy.

Although the Define File Reference dialog says "FileMaker will search for the file in the order the paths appear in the list," it actually gives preference to a file that has already been opened.

I've not found a way around this bug/feature.

-- Ward

This topic is 6805 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.