|
Eric, Make the field optional and do not require a mandatory entry. Testing for special characters is not an option; for example testing for a slash, while "n/a" may be a valid entry. Just my thoughts. Regards, Carel Teijgeler *********** REPLY SEPARATOR *********** On 25-8-05 at 11:31 Eric A. Wolf wrote: >I am trying to create a utility to prevent users from entering insignificant >data in a field. For example, if the user is required to enter a Contact >Name (which cannot be verified against any table), I can check for blanks >and issue an error. However, if the enter a ".", "X" or all "*", an error >will not be issue. Has anyone written something like this (or similar) to >handle this? > >I could write a routine to go through every character on the keyboard to >test IF fieldname = *all'x' but what about just checking for three AAA's or >999 in a 20 character field?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.