doesn't seem a point in doing that - why create even more ODBC load than u need to? <! ----------------------------------- Neil Clark Senior Web Applications Engineer mcb digital Tel. +44 (0)20 8941 3232 Tel. +44 (0)20 8408 8131 [Direct] http://www.mcbdigital.com -----------------------------------> ------------------------------------------------------------------------------------------------ Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message with 'unsubscribe' in the body to [EMAIL PROTECTED]
- RE: Storing passwords in database as one way hash Dave Watts
- RE: Storing passwords in database as one way hash Chapman, Katrina
- RE: Storing passwords in database as one way hash -... Neil Clark
- Re: Storing passwords in database as one way ha... Rob Keniger
- RE: Storing passwords in database as one wa... Neil Clark
- Re: Storing passwords in database as on... Rob Keniger
- RE: Storing passwords in database ... Neil Clark
- Re: Storing passwords in database ... Jon Tillman
- RE: Storing passwords in datab... Neil Clark
- RE: Storing passwords in database as one way ha... Jon Tillman
- RE: Storing passwords in database as one way ha... Steve Bernard
- RE: Storing passwords in database as one wa... Cameron Childress
- RE: Storing passwords in database as one way hash BORKMAN Lee
- Re: Storing passwords in database as one way hash Dirk De Bock
- Re: Storing passwords in database as one way hash Rob Keniger
- RE: Storing passwords in database as one way hash BORKMAN Lee
- RE: Storing passwords in database as one way hash Paul Johnston
