you are calling it again 21.
I was thinking about something like:
have base number 1
have build number (current 21)
have subversion number which tells that major changes happened.
so we will end up with 1.0.21
the thing is, if you have a fix for some bug or some little enchangement the build number is sufficient. but if major thingies has changed (like I noticed between 6 and 11)
the sub-version should be changed.
something like how the events are fired or how the form works towards windows.
a major change...
a good example is that if you add to build 22 the support (full) for win9x it will be called:
1.1.22
well, anyway it's your call, but this way could be easier for even me to keep track on the kixforms files and changes.
as I somewhat have all build you have mailed me on my harddrive.
_________________________
!download
KiXnet