I'll pick the cherries first here, then get to the hard stuff. First, a team of *1* needs source control. If your lead won't buy into it, take the initiative and step around him to his boss and sell him on the risks that no VCS brings to the team, the project and the company. Make sure to emphasis the risk for code loss and the costs associated with redoing lost work. Sell him on the economies of scale that can be found by enabling 2+ developers to work on the same codebase at the same time.

If you want to implement something from scratch, I'd suggested going SVN through the VisualSVN route. Quite literally you'll have your SVN server up and running in about 5 minutes. Take that and enhance it with TortoiseSVN to make your Update, Add Commit life a breeze. Great thing, both are free! Now some people are going to poo-poo me here for my next statement, but remember, the best tool for the job. In the case of a VB6 shop SVN will work, but **IF** your team hasn't run source control at all in their lives, you'll probably want to think about Visual Source Safe too. It sucks, let's be honest, but it is a tool that you can learn with. If you have confidence in the ability for you and your teammate to learn, skip it though and go straight to SVN.

The Pragmatic Programmer series has a good book on SVN. Another place to look for information on the "how" portion of using source control is Jeremy Miller's blog on codebetter.com. Look for his posts on the "Check-in Dance". They're the ones you'll really want to wrap your head around.

Having dealt with this numerous times in the past, now included, the hardest thing to read is that your teammate's lack of professional motivation is depressing. You have to watch that the passion void doesn't become contagious. The fact that he's like that will make it exceedingly difficult to learn anything useful from him. He just won't have progressed his knowledge enough to have a backlog of pertinent info to pass on.

One of the statements that I live and die by is "Don't let your job work you into irrelevance". Don't let them work you into a dying technology so that you're no longer marketable. Don't let them stop you from practicing the best techniques in your trade. If they won't change to let you do either of those, then it's time for a change. I know the economy is a scary thing right now, but if you feel that you're not going to get anything from this job (other than xx months/years on your resume), start looking for somewhere else to work. If you have 1/2 the skill that you show in passion and initiative, you should have little problem catching onto a team that will help you to grow.

Hope that helps and best of luck. Feel free to shoot me an email if you have any questions.

First of all having access to source control is non-negotiable. It is good that you have an idea where things need improving but is sound like the "lead" is not interested. You can stay there but you won't build your skill set. Really the only thing you can do is to do it the way the "lead" wants and start making a plan to get out of there. The lead will be there long after you are gone. I call those people fixtures because they aren't going anywhere. It will not get better, he/she wants things to stay the same. I don't want to sound negative but you will regret not being immersed in object oriented design, test driven development and agile development. I have worked on a team of two before and it is like an unpleasant arranged marriage. If you are not careful you will really start to resent the lead. It is best to just plan you escape. In the meantime keep yourself up to date by learning new skills, taking classes or studying for a certification. You may have to ride this one out since the economy is struggling but get out you must.