Thank you for the tips! It's not going to be for a bank, but it will include sensitive bank information in a graphical format (i.e. scanned checks). I will be looking at security from all standpoints (i.e. server, DB, application, firewalls, etc.), but at this point I'm trying to isolate one thing at a time.
BDKR, do you have any other suggestions for the DB, from a security standpoint? I've not read up on that side of DB's...just speed tests and the like. I'd hate to lose MySQL in this scenario...it's almost like an old friend. But, security is most important in this situation.
rlogin, yes, the DB will need to be designed. The banking information exists in paper format only, and is not tied to account information per se. (See above.) I've got a good design in mind for this...I will need to look into https, though. Thanks for the comments!
Scott...well, she see's the back of my head on special occassions.

But, inbetween I am lucky enough to have a basement to develop in, although I used to have an office in our old house, which I miss. That was really nice...
Thanks again, all!