Hello, new here, hootie hoo!

The test file below lays it out in detail, but basically I need a way to overcome the limitation of global containers not saving network user changes. I'm trying to create a "flag" to let different users know that a message is in there message box, this flag will be triggered by a button and it will have to be on every layout, this includes unrelated tables.

I have a test file for you to play with:

Usernames (no passwords) Admin, Moe

http://www.joelcardinal.com/_notes/redblue.fp7

I don't want to be a butthead, but if possible please give a working example of the solution--I will probably not understand the theory of how to make this work.

Thank You!

-Joel

Just don't use a global... use a regular container field. If you place it in it's own table with only one record, then any changes made to this field will be seen by all network users. You will have to use relationships to view this data from other tables, but you can just use the "X" relational operator for this and any linked layouts will view the color...

But you can't add a relationship between two container fields in separate tables that are not global. You can't even use an auto-enter calculation that refers to the initial container without a relationship.

So how do I get a container field to show the same contents that reside in a container field in an unrelated table?

Edited August 12, 200520 yr by Guest

How about a seperate table listing users. If a user has mail set a GotMail field to 1 and use a Calculation Container to display your jAlertContainer contents... If(AccountList::GotMail = 1;jAlertContainer; ""). I used a script step of Set Field [g_UserName; Get(AccountName)] to set a global containg the current users name on startup. This allows the relationship between the current table and the AccountList table.

example attached; user names are:

Joe Schmoe

Amy Andrews

Tommy Terrible

Franky Fingers

Admin has full access

MakeRed.zip

Oooh that sounds promising, lemme play with that, I'll let you know if I can incorporate it into my project. Thanks!

Maybe I'm missing something but there is no container changing on a different table.

Also, as a network user, I don't think the status of the alert would be saved once the file is closed.

Here is an example of what I was talking about...

match.fp7.zip

Thanks Reed, I'll test it tommorrow.

Maybe I'm missing something but there is no container changing on a different table.

Also, as a network user, I don't think the status of the alert would be saved once the file is closed.

The container that is showing the Alert uses the calculation - if(AccountList::GotMail = 1; ; else show nothing (=""). The status of the alert would be saved for each UserName in the AccountList table. If Joe Schmoe's GotMail field does not change from a 1 to a 0 in the AccountList table the next time his account is logged into the Calculated Container field would still show the alert. Each Users GotMail field is saved with their record in the AccountList table.

What isn't saved is the g_UserName as it is stored in a global field. This is why you use the Set Field script step at startup. This way you can have one field for all records that can store a different value for each user (Their Account Name). Since the RedBlue table matches with the AccountList based on g_UserName = AccountName when Joe Schmoe logs in it will show the status of his GotMail field... 1 = Show Alert, 0 = No Alert.

Edited August 13, 200520 yr by Guest

I'll be looking at both solutions again today, thank you for your time and help.