I agree with the above. Paper based systems are a problem in and of themselves. Most of us are getting less used to paper not more. Even email based "forms" are paper like and don't work that well. The thing I've found over the years is any process needs to be lightweight and not get in the way of the process. If it does, it won't be followed, or be randomly followed. The easier you can make it, the less resistance you'll get.

For VB or Web work, the tools automatically check out and check in files you work on and even give you a box for comments. Even then they're not always used unless someone "forces" the users to enter comments. Which is a big part of any VCS. You must have some type of administrative controls in place that force people to comply.

I've used VSS, but it was a hack and it only worked in conjunction with server side permissions to limit developers to a single db, scripts to look for changed objects that I could then verify were in VSS, buy in from management to enforce administrative penalties (they lost object DDL rights :cool, and a little training.

http://www.sqlservercentral.com/columnists/sjones/vcspart1.asp

http://www.sqlservercentral.com/columnists/sjones/vcspart2.asp