How FM behaves on a server

[spb]

I am wondering if anyone can point me to a white paper or something similar that lays out all the various aspects of FM that change when a file is being served? I currently know of two:

1. Global fields are no longer truly "global" when a file moves to a server. These fields now become different for each user.

2. Export paths can get confused. I export small text files for use in our DOS network. I have recently learned the hard way that if I set up a new export script directly in a file being served, then the path of that script becomes variable depending on the user. I had to pull a copy off the server, open it locally, rememorize the path, then reinstall it on the server. Now the path is the same for all users.

Are there any other aspects of FM that will change when a file moves to a server? Or some document that lists this stuff?

I would like to do some developmental work directly on served files, without pulling them off and on. But I don't know if I'm setting myself up for future trouble. External scripts, for example. This sounds like another path situation.

Steve Brown

[DonH]

I don't know of any papers, but that is a lesson I learned real quick. All paths are relative to the host of the served file, not the server. I had to make many many changes to fix problems associated with that bugaboo.

[spb]

Forgive a server newbie's ignorance. But when you refer to "the host of the served file," do you mean whichever user happened to log on first? If so, why is it different when a path is set up on machine A directly on a served file, and when the file is pulled off the server & installed on machine A's hard drive? In the latter situation, the path now seems relative to any machine logged in (after the file is reinstalled on the server). In both cases, the export script step is originating & memorized from machine A.

This does not seem to be a problem with external scripts, which are calling on information in other files, perhaps because the path is always the same, i.e., the server.

Steve Brown

[Vaughan]

I hope you are not putting the FMP file on a shared network volume for people to open... this is disaster, which is why FMP issues a warning before opening the file.

FMP files are shared by dedicating a machine to running FMP or FMS, and leaving the files permanently opened. users connect into the database through the "Open Remote..." command, or the Hosts button.

[spb]

No, I didn't make that mistake (thanks to dutifully reading this forum). My FM srever is running Win2000 and is wholly dedicated to serving FM. It performs no other functions. I've also insisted that the three people who need to access some files do so via the Hosts button & never "Open Remote." The rest of the users get where they need to go with a launcher file.

There is an NT server on our network, which runs the aging DOS application I am slowly replacing with Filemaker. During this interim period, I must import and export text files between FM & the DOS app. Hence my path confusion that started this thread.

Steve Brown

[Anatoli]

Steve,

1. Global field is common for all records, but on network is different for each user. When you open file with global field from server, the last values written to global when the file was used locally in single user FMP will show up as first values. Then any user can change those values but after closing FM all changes are gone.

You can develop as administrator layouts and scripts without shutting the server off or disconnecting users.

You must disconnect users when modifying database structure e.g. renaming fields or adding them.

You must shut down files on server if you want to change privileges or global fields.

[stanley]

You can find the FileMaker Server Best Practices white paper (and others) at:

http://www.pre1.com/about_us/about_our_technology/whitepapers.html

-Stanley