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 4637 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Hi everyone,

I am using filemaker pro 11 advanced ,my problem is that i am using global field (idd) to store last record and in new recored i am increasing the idd field by one ,the script which i attach is working fine but when the filemaker is forcely quit the idd global field is not giving the proper results.can anyone know why its happening

post-101539-0-15025000-1336548088_thumb.

Posted

Hi randhir

From Filemaker:

Global field values are global to the user, not to the database. Each guest maintains values in their global fields separate from other guests.

When a guest opens a file, the global field values are copied from the values for the host into the guest. If the guest's global field values are then changed, such as by running a script, they are changed just for that guest. They are not changed for the host or any other guests.

This is intended behavior to facilitate using global fields with scripts. The only way to reset the default value for a global field is to reset it from the host computer. Changes are saved only when the file is closed.

One way to store information between Filemaker sessions is to use a 'system' table and to have your idd field in that table. I set up system tables as follows.

A numeric field called UID - a unique identifier value for the system table records

A field such as idd - this is the data that needs to persist between Filemaker sessions.

I create just one record in this table, and set the value of UID to 1.

On the relationship diagram I link the UID field in system to a UID field in my main table, and set the connection to be the union x operator. This makes the system table visible to every record in my main table. As there is only one record in the system table, every time I update system::idd it is always the same field, and It will retain it's value when the database is closed.

For this to work, the field UID in your main table must have a value. This can be done by setting this field to auto-increment serially by 1, and not allowing users to modify it. If you don't have such a field in your main table, set it up and then run a replace field contents on it to update the serial numbers so that it has a value in all your existing records.

HTH

Brian

Posted

Why aren't you using regular FM-generated, auto-enter serial numbers? You can then use calculation which concatenates your date and serial ... without possibility of it breaking and without script.

Posted

hi, everyone

when you forcely quit the filemaker the new records will not saved unless you press enter button and save the records

Posted

hi, everyone

when you forcely quit the filemaker the new records will not saved unless you press enter button and save the records

Yes that is right.

Same thing happens when you pull the power plug out of the wall while the computer is running.

Don't force quit FileMaker!

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