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

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

Recommended Posts

Posted

I have 4 computers each with their own version of Filemaker 7, sharing a file from a Remote (ethernet link) computer. Making changes to a field remotely, does not show up on the Main File. This is happening either when making changes manually or using a "Script". The File has a relationship which looks for the IP address of the "Original" File. I thought the purpose of remote files was to allow changes over a Network? Making a new record remotely seems to work fine ? ALL Access privileges required for the action have been authorized via a "Priviledge Set"

Posted

Are you hosting the file by turning on Filemaker Network Sharing, and then on the client machine, use the open remote... command and seeing the local host, or specifying its IP address?

I'm not sure I understand how you're doing it, but sharing it the way I just described works as expected between any combo of MacOS 10.3.3, XP sp1, and 2000 sp6.

Posted

Yes, I am Turning on the Network Sharing then Opening Filemaker on the remote machine then opening the desired file using "remote". I have a Serial Number Field on the Layout and when I update it remotely it does not update on the Original or if I modify a related field on a layout it shows the new information on the remote screen but does not change the Original (related) record ?

Posted

P.S. I forgot to mention The Database being used is a multi-file database converted from a version FM 6 and adjusted as required. As an interim measure until I can create a single File Multi-Table Database.

Posted

If I understand the literature properly I only have to move to another field in order to "Committ" the record, and I have done this. I have also tried changing layouts then returning.

Posted

Moving to another field doesn't commit, you need to "click out" of the record, or move to another table. Moving to another layout based on the same table also will not cause a commit.

You might want to just add a Commit Records/Request script step.

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