Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

slow response tied to file references?

Featured Replies

  • Newbies

When setting up File References, which is the best syntax to use? We have a file, call it “navigator.fp7” which opens the other files in this solution. The File References to those other files read, for example: “file:names.fp7;fmnet:/*.*/names.fp7.”

Is the fmnet reference necessary? These files are to be hosted on either single user local machine, peer to peer, or FileMaker Server.

Here is our problem: when using the file reference syntax “file:names.fp7;fmnet:/*.*/names.fp7,” and using FileMaker Pro 8.0.1 or 8.0.2 as a peer to peer host, or when using FileMaker Server 8.x as the host, other FileMaker Pro 8.x Macintosh clients take 15-20 minutes to open the solution. FileMaker Pro 8.x clients for Windows open the files in 10-15 seconds.

FileMaker Pro 7.x for Macintosh does NOT have this problem.

Why?

It appears that removing the “fmnet” reference and using only the “file:” reference solves the problem.

So, when building file references for files that will be used 1) cross platform or 2) single user or 3) peer to peer or 4) server-client, what syntax should be used for File References?

My conversations with FileMaker’s tech support make me think we should not use either of the above.

according to FM:

“file:[filename.fp7]” causes the FM host to search the entire host machine.

“fmnet:/[iP]/filename.fp7” causes the host to search the network for the files, which as the host, is pointless.

I glean that the correct way to build these files is to hard code the directory path and tell our users to put the data there and nowhere else.

For example: filewin:/driveletter:/directoryName/filename

And: filemac:/volumeName/directoryName/filename

So, HOW do you plan for cross platform, or peer to peer, or server-client implementation if you have to have these multiple file references?

For files hosted from the same directory as the current file, simply use the file:filename.fp7 syntax. Only use filemac and filewin if you have files residing on the client workstations that are referenced by a hosted file. Use fmnet if you need to refer to files that are hosted on a different machine than the current file.

Create an account or sign in to comment

Important Information

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

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.