Instead of patterning the field to $MENU$ why dont you use the Display-Type as a drop down then.. it works exactly the way $MENU$ was designed to work except that you can't type into the field but select from the menu only...
Cheers Joe D'Souza Remedy Developer / Consultant, BearingPoint, Virginia. ----- Original Message ---- From: Rabi Tripathi <[EMAIL PROTECTED]> To: [email protected] Sent: Tuesday, March 13, 2007 6:11:54 PM Subject: ARS 7 bug: $SCHEMA$ on menu qualification I just figured out that if you have $SCHEMA$ keyword on any menu's qualification, it behaves very differently in ARS 7 (vs ARS 5, and perhaps ARS 6.x as well). In older versions, $SCHEMA$ always expanded to the name of the form where it is attached. In 7.x it gets two different values, depending on the context. For example if a menu gets its values from MenuSource form and is attached to forms Form1 and Form2 $SCHEMA$ in the menu's qualification always expanded to mean Form1 or Form2, depending on which form are you at. Not any more. In 7, when the menu is opened on any form , say Form1, $MENU$ in the menu's qualification still expands to "Form1" and you get the expected values in the menu. However, if you have $MENU$ specified as the pattern for the field (fields's Properties, Attributes tab) save operation will most likely fail because $MENU$ expands to "MenuSource". It broke my old workflow, so I need to redesign my menus to not have $SCHEMA$. Fun. I have ARS 7.0.1 p1, AIX 5.2, Oracle 9.x. I tested with windows client only. ____________________________________________________________________________________ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. http://answers.yahoo.com/dir/?link=list&sid=396545367 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
