It's strange that the search action is failing, because this should work
fine. Plop the <@SQL> tag in the Search Action results or turn on
debugging and see what the query is. Maybe there is some other problem at
work.
If it turns out the problem is that your DB or driver can't make sense of
"WHERE T.PASSWORD = '@!*%'" then you might need to check for those
characters when the person sets or resets their password.
P.S. Isn't that how you swear when you're a cartoon? @&*%!
On Fri, 24 Jan 2003, 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
>
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
