Display Current Username in Layout Header

[Rodd]

I have a standardized layout template that I'm want to put current username on. When you look at the layout in browse mode, it shows in the field area, yet when I click on the field, shaazam, the username is displayed. Do I have to create a username field in any table where it's displayed on a layout? That seems like overkill.

[Ted S]

You could create a global text field and a script that runs on startup that puts the user name into the global field. Since globals don't have to be related to anything the contents should show up on any and every layout you place the global field on.

BTW. Greetings from Mpls.

[Rodd]

Interesting. I added a field to the layout's supporting table, as a global calc field (my data is separated into a different file). I also added the same field to the primary table in the separate file just for giggles. When I use the local reference, it doesn't contain any data. When I use the remote reference, it shows the username only when you click into the field.

I'm thinking its pretty nice out right now. Makes me want to leave the office.

[Rodd]

Wait, I forgot the script. It works perfect.

Maybe I should go for a walk outside. I'm in Chaska btw.

[Ted S]

In my system I have a "session" table that has nothing but a bunch of global fields in it. When the user opens the main file I have a script that automatically tries to match the user's account name to an account record. (I have an account record for each user) If it finds a match then it populates the session table with different things such as the user's full name, title, phone number, email address, logon time, IP address, etc. Then elsewhere in the system if I ever need to display the current user's title for instance, I just place that field from the session table on my layout and I'm good-to-go. I don't have to create relationships everywhere.

It works pretty well. I do not use it for anything related to security however. I use native FM security exclusively.

Yeah, sounds like a good night to stop by the Lions Tap for a cold one on the way home.

Edited September 28, 2007 by Guest
Spelling

[Rodd]

That sounds like a good idea. And since it's global, you can have it in just one place at startup. I'll have to implement that.

I do have one that you may be able to help as well. I have a layout that has a master record on the top, and a tabbed detail area below. No big deal. But in the detail area, I have a portal. This portal, if i were to put all the detail records in it, would be way to wide. So I thought, hey, why not create a temp table of the same layout as the detail and then when you click on a portal row (I created a button action tied to a script), it would get the portal data and put it in fields below it so you could edit the portal row. Everything worked great, until I tried running it on another machine looking at the same record. If you go to one machine and click the portal record, it updates on both machines. How can I stop that because the general idea works in single user mode.

Thanks

Rodd

I have to go to a football game tonight, so no Lions tap or beer.

[Rodd]

Here's a screen shot of the layout

[Rodd]

Well, it must be the act of writing it out that helped me. I changed the temp table to global fields (thanks to your earlier suggestion) and now it works as well.

[Ted S]

Very cool. BTW, nice looking layout!