Seems I remember some exceptions to the case/db relating to $USER$ and/or $GROUP$. Keywords are not queried from the db, but from some type of session data, which would be handled by the client/arserver, not the db server.
Axton Grams On Jan 15, 2008 9:43 AM, Rick Cook <[EMAIL PROTECTED]> wrote: > ** Case sensitivity is determined at the DB level. If your DB is > case-sensitive, you are correct in your assumption: App Director ID != App > director Id. > > *Rick* > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Sokol, Brian > *Sent:* Tuesday, January 15, 2008 6:29 AM > *To:* [email protected] > *Subject:* Case Sensitivity in Run If Qualification > > ** > > I have an AL qualification of $USER$ = 'App Director ID'. If the case does > not match should the AL fire? I didn't think the case mattered but it will > not fire if there is a case difference. > > Brian Sokol > Manager, Desktop Services > Scholastic Inc. > 557 Broadway > NY, NY 10012 > (212) 343-6494 > *http://www.Scholastic.com* <http://www.Scholastic.com> > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
