Acknowledge an asterisk as a string
in [General]
|
From: kidkosmo on 31 May 2010 23:15 Hi, All, Is there a way to have Access acknowledge an asterisk as a string value rather than a wildcard? I would like to add validation to a field that will not allow and asterisk to be added as part of that field; however, the validation appears to recognize that value as a wildcard and does not allow any value to be entered. Thoughts, ideas? Thanks!
From: James A. Fortune on 1 Jun 2010 00:05 On May 31, 11:15 pm, kidkosmo <kidkos...(a)yahoo.com> wrote: > Hi, All, > > Is there a way to have Access acknowledge an asterisk as a string > value rather than a wildcard? I would like to add validation to a > field that will not allow and asterisk to be added as part of that > field; however, the validation appears to recognize that value as a > wildcard and does not allow any value to be entered. > > Thoughts, ideas? > > Thanks! Try: SELECT * FROM MyTable WHERE FieldName LIKE "*[*]*"; to return records from MyTable where FieldName contains an asterisk. Maybe NOT LIKE "*[*]*" will give the opposite. James A. Fortune MPAPoster(a)FortuneJames.com
From: david on 1 Jun 2010 06:16 Or, if you want that as a validation rule, LIKE "fred[*]nurk" applied to a textbox or table, that only accepts fred*nurk (david) "James A. Fortune" <MPAPoster(a)FortuneJames.com> wrote in message news:9ae1c0f5-95c7-4aa5-b8ab-58ccab311284(a)q23g2000vba.googlegroups.com... On May 31, 11:15 pm, kidkosmo <kidkos...(a)yahoo.com> wrote: > Hi, All, > > Is there a way to have Access acknowledge an asterisk as a string > value rather than a wildcard? I would like to add validation to a > field that will not allow and asterisk to be added as part of that > field; however, the validation appears to recognize that value as a > wildcard and does not allow any value to be entered. > > Thoughts, ideas? > > Thanks! Try: SELECT * FROM MyTable WHERE FieldName LIKE "*[*]*"; to return records from MyTable where FieldName contains an asterisk. Maybe NOT LIKE "*[*]*" will give the opposite. James A. Fortune MPAPoster(a)FortuneJames.com
From: John Spencer on 1 Jun 2010 09:55 If you just want to eliminate asterisks then the validation rule could be Like "*[!*]*" Or NOT Like "*[*]*" John Spencer Access MVP 2002-2005, 2007-2010 The Hilltop Institute University of Maryland Baltimore County david wrote: > Or, if you want that as a validation rule, > > LIKE "fred[*]nurk" > > applied to a textbox or table, that only accepts > fred*nurk > > (david) > > "James A. Fortune" <MPAPoster(a)FortuneJames.com> wrote in message > news:9ae1c0f5-95c7-4aa5-b8ab-58ccab311284(a)q23g2000vba.googlegroups.com... > On May 31, 11:15 pm, kidkosmo <kidkos...(a)yahoo.com> wrote: >> Hi, All, >> >> Is there a way to have Access acknowledge an asterisk as a string >> value rather than a wildcard? I would like to add validation to a >> field that will not allow and asterisk to be added as part of that >> field; however, the validation appears to recognize that value as a >> wildcard and does not allow any value to be entered. >> >> Thoughts, ideas? >> >> Thanks! > > Try: > > SELECT * FROM MyTable WHERE FieldName LIKE "*[*]*"; > > to return records from MyTable where FieldName contains an asterisk. > Maybe NOT LIKE "*[*]*" will give the opposite. > > James A. Fortune > MPAPoster(a)FortuneJames.com > >
|
Pages: 1 Prev: Window 7 live mail Next: BartShell Module has Stopped working. How do I correct this. |