Solution needed for field displaying across records

[m.r.mymandms]

Hello.

Is there a field or anything in

Filemaker which is like a global field in that the data in

it can be viewed across all the records at all times BUT can be viewed and edited

at anytime by any person logged onto Filemaker on a network? Oh, and the

solution can't be too complicated either! I'm an old novice.

[brian rich]

There is no Filemaker global field type that can be shared between users in the way you describe.

You can achieve something like you describe within a single Filemaker database as follows - I hope this doesn't sound too complicated

Set up a table called PREFS (for example). In this table add two fields, say UID and sharedField. UID is a number field; sharedField is whatever data type you want the field that all users can change to be - text, number, date etc.

Now create just one record in the PREFS table. Set the value of UID to 1. Set the user privileges so that they cannot add or delete records in the PREFS table, so this table will only ever contain one record.

Every other table in your database should contain one field that is a unique table UID for the record and is set so that the field automatically gets a unique serial number each time a new record is created, and so always has a value.

On the relationship diagram, join UID in the PREFS file to the table UID for each table, and make sure that you select the UNION operator to join the fields - that is the x symbol at the bottom of the operator list. This means that the relationship from each table to the PREFS table is always true so any other fields in the PREFS file will be available from every record in every table. Since there is only one record in the PREFS file, then your sharedField is always the same one, and is effectively global for everyone.

I use this type of structure with several fields on it, which store settings or constants that are available to all users of the database.

There is a BUT here... I would be VERY CAUTIOUS about allowing all users to change this field freely. For example, if one user changes the field and another user changes it immediately afterwards, then the first user may not see the results expected. If a user has made a change to this field and goes off for a cup of coffee without clicking or tabbing out of the field, then other users would be prevented from modifying the shared field, or modifying any data on any layouts where the shared field is displayed. If you really need this facility, then have any changes to it managed through scripts.

HTH

Brian

[m.r.mymandms]

Wow, I appreciate all the time & effort you put into this solution. Thank you Brian. Your solution maybe and probably is over my head though I may give it a go. I have a temporary solution, kind of sloppy but it's working right now. I created a field and then attached a script and a script trigger to it that has the replace dialogue open up and paste the field data to all the fields in the file in that field. I used an exit script trigger. I'm also creating a text field and hopefully writing a script that will record & paste all the info ever used in the field as a sort of record so if anyone accidentally deletes content that needs to be there i can go back in and just paste it back in. If anyone gets in that field and deletes the contents in it then replaces it with their own I'll have a backup. I would like to protect the field with a password but that isn't available in filemaker either I guess. The data contained in this field isn't ALL important but important enough to try to protect apparantly. My best friend married a programmer and I married a mechanic. My car runs great but today I'm jealous of her.

[brian rich]

Hi m.r.mymandms

I created a field and then attached a script and a script trigger to it that has the replace dialogue open up and paste the field data to all the fields in the file in that field.

In case you weren't aware, the replace field contents script step is not multi-user friendly. If your run this step then it will only update records that are NOT being edited by other users. Unfortunately, the function doesn't tell you that it failed on some records, nor which ones, so your data will become out of step.

Brian

[Ron Cates]

Maybe you should explain the purpose of this field and how it will be used. Not just "I need a field that all users have access to accross all records". That's what you believe you need but there may be other ways. Tell us what kind of information it needs to hold. What that information is used for. Does it change? Who would change it? etc. Give us the user scenerio you want and maybe there is a better way to accomplish the over all goal that someone here can suggest.

Some thoughts without much info to work with;

1. I think Brian's suggested solution is probably going to be the answer. It reads pretty complicated but it's really not. If it turns out this will work we can surely help walk you through setting it up.

2. Maybe this could be accomplished by setting a global variable with an open script or some other technique. We wouldn't know without some more idea of the actual purpose.