>What tools do you use besides VSS for debugging/version control? I'm always interested in what others do, particularly on largish projects.
>

From VFP's standpoint, the most significant ones are ATS, which tracks bug reports, W3 Investigator, a tool that lets me track keystrokes/mouse actions that can cause an error, and a strong error handler that tracks the state of everything on meltdown. Lots of other tools to look at things outside the VFP environment.

The other important tool is being smart enough not to rely on testing on my development machine before releasing code. No one in their right mind would run a production environment with anything nearly as sick and twisted as what I develop under (and if I have to support them, I wouldn't let them!) and I catch a lot of dumb assumptions based on things I may have installed already or configured in a particular way by testing on relatively clean machines - I have a test box that has an IDE drive in it, that I've done base installs of each major OS I support for and shot images to a tape; when I want to test, I blow away the IDE drive, restore a pre-built image, and start from scratch; I can make standard client configs and put them in place in the same fashion (PowerQuest's DriveCopy Pro pays for itself very quickly.)

>>As to my causing a bug, I own lots of debugging tools; I count on having to seek out a termite or two that I may drag in kicking and screaming accidentally.