Yesterday I was having some odd performance issues with my Mid-tier users and eventually my Admin tool kept locking up whenever I tried to open any form on my production server (7.0.1 p6 on Windows). I ended up bouncing the service and then for some reason all of my character fields that had the $MENU$ pattern match set refused to actually match anything. I had one user call me about a field on one particular form so I removed the pattern match and changed the field from Edit to Drop-Down (now that all the clients have been upgraded to version 7). Then a few hours later a different user reported the same problem on a field in a different form. By early this morning I had 3-4 other fields reported with the same problem.
The pattern match on all of these fields worked fine before, does anybody have any idea why the $MENU$ pattern match would suddenly fail globally across multiple fields on multiple forms? I ended up exporting a full definition file and doing a search for the string "pattern : $-107$" which let me find all the remaining fields with the menu pattern match so that I could proactively fix those before getting user complaints. -Rick _________________________________ Rick Westbrock PETCO Telecom Engineer [EMAIL PROTECTED] _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
