I'm just basically going to agree with szlamany and DeadEyes said, as their advice here is sound.


Like DeadEyes said, you should have a proper front-end for SQL Server. Access is capable to a degree, but development times are much longer, and you have a heavily reduced feature set. There is also the issue that Access databases will always find a way of getting corrupted, which means that you will have to reset it (no good if you aren't around when it happens).


I don't recommend going back to college, as I did 6 years of college/University courses, and have honestly learnt far more relevant/useful information from a few one week courses (and much much more from websites, particularly this one!)


VB.net is a good idea, as Microsoft are commited to it for a good few years (VB6 has basically expired, so it's best if you don't start learning it!).

It would be best to get a good grounding from somebody who knows what they are doing, so check out the VB.Net courses near you, and make sure the company pays - even thought you might enjoy it, they will be getting the benefit! After the course you can expand your knowledge with the .Net help, and online.