When you're evaluating the password, you could check for the length (@length) and do a '@keep' specifying only letters and numbers, etc, and see if they are the same length in addition to seeing if the same thing was entered twice. That way they can never choose the illegal characters in the first place.
Jason
On Friday, January 24, 2003, at 08:35 AM, Dan Stein wrote:
I need to trap for @#_ etc. It seems that if someone uses those types of--
character in the password that the search action can't find them.
So I either need a way to deal with them in the search or trap for them in
the password setup.
Dan
-- Dan Stein
Digital Software Solutions
799 Evergreen Circle
Telford PA 18969
Land: 215-799-0192
Mobile: 610-256-2843
Fax 413-410-9682
FMP, WiTango, EDI,SQL 2000
[EMAIL PROTECTED]
www.dss-db.com
_______________________________________________________________________ _
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
____________________________________________________________________
Jason Pamental, President [EMAIL PROTECTED]
Bathysphere Digital Media Services, Inc. http://bathyspheredms.com
____________________________________________________________________
Tel: 401.490.6830 Fax: 401.490.6831
________________________________________
A North American Distributor for Witango (http://www.witango.us)
Rapid Web Application Development - XML Execution Engine
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
