Search:

Glad you got it working. It's not so much 'bad practice' as just wrong. You declared two references to JPasswordField, only one of which you assigned to a JPasswordField object. The other one's value...

search your text file for "JPasswordField". It should be in there only twice - once when you declare the reference pfPword and once when you use the JPasswordField constructor. I count more than two...

Heheh - there's another thread on the forum today about this. How many times have you declared pfPword?

Why is pfPword null? Isn't that your password control? I'm guessing it's not the NPE that the API doc warns about in JPasswordField.getPassword() - or the stack trace should start inside that method....

There's not much in there that could be throwing an NPE. Which is line 100 in db.java? If you've edited the file since you posted the stack trace, make sure you select the line on which the Exception...

Copy and paste it. You've read the API doc for getPasswordField and seen that it can throw a NPE?

It's not difficult, you just need the magic incantation in Java.

Let me google that for you

MessageDigest is what you need. It looks a bit daunting at first, but most times you use it it'll be...