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

Recommended Posts

Posted

No, I think that this is the quickyer way, given the fact that the field "OnOff" can't be a calculated one.

Also may be that changing that field from text to number ( with 1 and 0 formatted to show On and Off ) can make the script even quickyer.

But the script must be modified if you want to mantain a found set.

Posted

A convenient way to deal with this situation would be to store the ID of the selected record in a preference field. This could be a global field (for the current session only) or a "real" field in another table (for a permanent change, affecting all users).

Trying to replace data in multiple records can easily fail in a multi-user setup, where some records can be locked.

Posted

Hi comment

If I understand you correctly you suggest to store the record Id corresponding to the field value "On" into a field and after, if another record get the "On", we will set to "Off" the field with that record Id and will keep the new record Id.

But how exactly, always with a script ?

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