>>>>Hello,
>>>>
>>>>We use version numbering for our VFP executables:
>>>>
>>>>3.14
>>>>3.15
>>>>etc.
>>>>
>>>>We always used only two digits for the second number, but the numbers increase too quickly. I wonder if there is a rule how many digits the second number should be, I did not want to use a third number, because then I would need to change some logic that we created many years ago. So could I create versions like
>>>>3.140
>>>>3.141
>>>>3.142
>>>>etc?
>>>
>>>How about using Revision number -- especially if you're trying to keep track of differnt builds after bugfix or minor program tweaks.
>>
>>I know that would be the best approach, but we would need to change that in many different places, tracking documents, issue reports from clients etc, code that was written more than 10 years ago.
>
>The problem I see you'll be running into with the scheme of:
>3.14
>3.140
>3.141
>3.142
>...
>3.149
>3.1410
>3.1411
>...
>3.15
>
>would be that 3.142 might end up being considered "newer" than 3.15 within the OS.

I always thought version 3.4 is higher than 3.39?

I could work around to stick consitently with 3 digits. Only I never see version numbers of other programs using three digits, but that may be just a preference.