There are so many, many ways this could go wrong on you. The first thing to do is to stop doing it like that!
The first thing to not do is build SQL commands by concatenating strings. This isn't causing teh problem you are talking about, but it does leave you wide open to an SQL Injection attack, which can damage or destroy your database. And given that this is a website, that means I could go to your default page, type in the username or password box and delete your Access data. Or log in as any user without knowing their password...
Use parameterized queries at all times!
The second is "Never store passwords in clear text" - it is a major security risk. There is some information on how to do it here:
Password Storage: How to do it.[
^]
After that you need to start looking at what is happening - so either run this in the debugger and see what occurs (it's probably an exception, but unless you find out where it is you can;t even start to fix it). So
try...catch
blocks and logging are the order of the day, combined with using the debugger to follow what is actually happening.
But...why are you "brewing your own"?
Why not let the system handle it:
Introduction to Membership[
^]