Randem Systems Support Board

I think I now follow the VB6 logic.  What's shown in the version number entry box is the LAST (previous) compiled version.  If Auto Increment is checked the version number of the ensuing compile is incremented.
 
I'll just stop using Auto Increment and control the version number myself.

I've confirmed through testing that what you say is correct.  When I turn Auto Increment off InnoScript uses the version number I enter in the compile options.  But, unless I'm missing something, it seems to me that the VB6 Auto Increment feature is unintuitive and illogical.  
 
Given the capability to enter a specific version number for a given compile, why would VB6 increment it for THAT compile?  It seems that the Auto Increment feature should apply to the NEXT compile.  In fact, that's what seems to happen with Auto Increment on.  For example, if I specify version 1.0.1 for a compile, the next time I compile and check the options the version entry is preset by VB6 to 1.0.2.  But, 1.0.2 is used for the previous compile and 1.0.3 for the current compile.
 
I guess there's another possibility here that seems logical -- that is, Auto Increment places two version numbers in the VBP file, one for the current compile and one for the next compile.  I don't know if that's the case but if it is InnoScript could be picking up the wrong version numbber.

InnoScript does not increment the version number. What is most likely happening is you have Auto Increment set on your project and when you compile it compiles the version you see then increments the project version number in the VBP file. This is what InnoScript would be picking up from your VBP file.

InnoScript is incrementing by one the version number used in a VB6 compile.  For example, if I set the version number to 1.0.1 via the VB6 compile options, the script generated by InnoScript show a version number of 1.0.2.  Why?
 
I am using Version 8.1 Build 4.