Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

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

Recommended Posts

  • Newbies
Posted

We have been using Filemaker Server to run several databases, including a set of 5 relational files. Everything ran smoothly from FP7 to FP8 upgrade, including all related DB files. Our server is on a PC (Windows XP I believe, FP8), all clients are Mac OSX (10.4.8) running FP8. I administer the databases using the Server Admin program from my Mac.

Recently, I needed to add another related database. To do so, I copied the related DB files to my local hard drive (after closing them from the Admin Server), set up all new relationships with existing files (including some calculations fields, merge fields incorporating data from several of the files for labels, etc. . .). Also duplicated the privilege sets and users for access for the new DB. Everything looked great when running tests on my local disk - all new fields and calculations with related files worked smoothly. I then transferred the new DB back onto the FP8 server drive. I closed out all related files (using Server Admin) and established the same relationships with the new DB as in my local drive test using FP8. I then closed out of FP8 and opened all the DBs with Server Admin.

Now, when I open the DBs remotely, I get a warning that this is a shared file, as if it does not realize the I am opening through the server. I only get this warning in cases where I am relating to the new DB file, or from the new DB file to one of the older files. All prior relationships among the DBs do not have any problems even though the files appear to be essentially the same as the new one (all preferences and file options, including privilege sets look like they are the same).

I seem to recall having a similar problem with FP6 Server with relationships not working so well on the server since the files are shared and the "main" DB would give you a warning when trying to use a related shared file. Since upgrading, this problem seemed to be resolved. . . until now.

Please note that I am not a pro user so my "protocol" above may be completely whacked. We have been using our server successfully for several years now with a few hiccups that I have been able to figure out. Any help here is appreciated.

Thanks.

Posted

Have a look into the file references (file -> define -> file references ). Great feature since version 7 to make this editable.

Sounds as if you saved some local paths there.

Tidy them up and leave for each reference only

file:name

if they are on the same server.

This works locally as well if the files are in the same folder.

-jens

  • Newbies
Posted

Jens,

You were right. Changing them to just file:name worked. Everything is running smoothly now.

Thanks for your help. Now I know to check these in the future for new relational files.

Thanks,

Nathan

Posted

When developing on these files off line, keep them all in a folder at the same level. That way when you define the file references, they will take the relative path. Maintain that folder on the server, and the references will remain as well.

Steven

This topic is 6657 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.