asked on

Button Name Label Change Formula Anomoly

Great Strange Question for everyone.
I have a formula for a button so that based upon a DBlookup, the button name changes each time it's pushed based upon the return value of the prior push. Here is the name label formula.
key := CMsub_sys + "PkgApprovals" + @Middle(CMpkgID;2;2) + CMpkg_status;
@DbLookup(""; ""; "CMapprovals";key; "CMstat_to")

The problem is. The return values can have a value like CM_APPROVAL (with the underscore). When the button is displayed the name that appears is CMAPPROVAL no underscore. However in the actual lookup and the view and the value in the form that creates the view the underscore is there as part of the fields actual value.
Why is the underscore being removed in the button name display ???
Real strange.
Thank you
Paul

ASKER CERTIFIED SOLUTION

Bill-Hanson

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

qwaletee

Hit the nail on the head. Notes uses underscore as part of form names, agent names, etc., to indicate that the following letter is an accelerator for the menu. Agents work that way in the ACTION menu. The Action menu consists of the following elements:

1) Fixed, context-sensitive elements that are controlled by Notes itself, not the template. For example, whena document is highlighted, tghe LOCK DOCUMENT item on the action menu is automatic.

2) All agents in the tenplate

3) All ACTION BUTTONS in a view, form, or subform

Because of item #3, Notes wants to offer the developer an option to specify the accelerator key for the action name. So, wherever you place the first underscore in the name, it is not interpreted as an underscore to be displayed in the name, but as an indicator that the next letter following should be underlined in the menu, and treated as a hotkey within that menu.

Note that you can't change this behavior even if you elect for the action to be treated ONLY as a BUTTON and NOT on the action menu.

The seocnd as subsequent underscores are not given special treatment, so Bill's advice will work. I'm only epxlaining why this is so.

pratigan

ASKER

Hello Bill,
Your absolutely correct. I did some further testing yesterday after posting the question and I worked with different special characters and I found the resultant to be exactly what you explained. I have already incorporated the doubling of the underscore which resolved the issue.
Thank You both for your feedback !!
Happy Holidays !!
Paul