Best way to handle Universal (static) data for opening URL - admin panel?

[Tony Martin]

I have a set of static data that's part of a web string.  The users open URL's using buttons and I use scripts to do that.

I'm trying to figure out the best way to store that data without storing it in the open url script, because it can change from time to time (not too often) and it can be a pain to change it from the script.

I was thinking of creating an ADMIN panel (ADMIN table actually) where the various data could be stored in text fields, but this isn't effective because the table isn't related to any other table.

Anyone with any ideas on this one?  Thanks in advance.

[comment]

I believe the common approach is to create a single-record Preferences table (what you call an ADMIN table) and use a startup script to load the data into global fields and/or variables which can be accessed from anywhere.

In the past it was suggested to use global calculation fields to eliminate the need for a script: 
https://fmforums.com/topic/39420-preferences-table-relating-to-all-tables-in-the-db/?do=findComment&comment=183791
https://fmforums.com/topic/52466-unrelated-table-needed/?do=findComment&comment=246238

But I am not sure if this method still works with recent versions:
https://fmforums.com/topic/89185-filemaker-12-migration-server-side-scriptmaker-does-not-set-global-fields-anymore/?tab=comments#comment-409077

 

 

Edited January 30, 2020 by comment

[Fitch]

I vote for single-record prefs table that loads into globals at startup.

Global calcs make my head hurt:

https://blog.jsmall.us/2008/01/behavior-of-filemaker-global.htm

[comment]

2 hours ago, Fitch said:

Global calcs make my head hurt:

https://blog.jsmall.us/2008/01/behavior-of-filemaker-global.htm

It's actually not that complicated. The relevant point is #10, where it says that a global calculation will NOT be updated for other users (and, presumably, for subsequent sessions of the current user) following a modification of a referenced field.

However, it's been a long time since Ray has written his summary and the behavior may have changed.

 

[Fitch]

Oops I meant global calculated fields, that's what I get for multitasking.

>> I guess I've just not found a compelling use for global variables vs. other techniques.

Edited February 4, 2020 by Fitch

[Tony Martin]

I'm an idiot - the best way to perform this function (at least the way I wanted to do it)  was with a table "X" (cartesian) join to each tables key_ID fields.  Works brilliantly.  Thank you guys for the ideas!