Guys. If you ever have anything worth sharing email it on over!
Paul. I usually use CFD fields in combination with roles. If you have a role called [Admin] then have a CFD called isAdmin. Its formula is simply:
@UserRoles = "[Admin]"
This equates to a Boolean style value which can then be referenced in all other fields and formulas. For example, a Computed Text area could then compute to:
@If(isAdmin; "Welcome Admin"; "Welcome User");
And hide-whens simply refer to the field by name. You can have as many of these fields as there are Roles and place them in all in a common subform, included on all Forms.
Luc. That client ended up settling for a 3rd party analyzer tool that churned through the W3C style logs that the server can export. Not much to it really.
Guys. If you ever have anything worth sharing email it on over!
Paul. I usually use CFD fields in combination with roles. If you have a role called [Admin] then have a CFD called isAdmin. Its formula is simply:
@UserRoles = "[Admin]"
This equates to a Boolean style value which can then be referenced in all other fields and formulas. For example, a Computed Text area could then compute to:
@If(isAdmin; "Welcome Admin"; "Welcome User");
And hide-whens simply refer to the field by name. You can have as many of these fields as there are Roles and place them in all in a common subform, included on all Forms.
Luc. That client ended up settling for a 3rd party analyzer tool that churned through the W3C style logs that the server can export. Not much to it really.
Ferdy. Domino XHTML is an oxymoron ;-)