>Nope - but we have to have approval from the 'powers that be' to put a new one on line. That means that anything but emergency bug fixes are going to take a day or 10 - And even the bug fixes seem to come in clusters with a single EXE. Hmm... Could it be that I caused a bug when I fixed a bug? No, never happen.......
>

My own rule of thumb has been if there are significant enough code changes to warrant stuffing the change up to SourceSafe before testing (I'll make revisions to comments and such at times and save back to SourceSafe, too, and this doesn't warrant a rev) there's at least a minor revision. Clients may see jumps of 75-100 in minor revision levels between .EXE releases. Following this makes it easier to backtrack to exactly the code in place when tracking down a mite or two.

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.

>
>>I guess I'm the only one turning out a new version number every couple of hours (minutes at times) while debugging...