Thanks Devaraj
The problem with this though, is that if I have version 34 of a file deployed and somebody comes along and deploys version 29.1.1 of a file (which I don't won't to be deployed because it's an earlier version), the code will turn it into version 2911, which the script will think is a higher version number than 34...
Just to clarify, the script I'm working on is used for the purpose of making sure that earlier versions of scripts cannot be released into our production database, when there is a later version of the same script already deployed.
Version numbers with the dots in, are what we call parallel version numbers. If I have version number 29 of a script deployed, and a developer wants to work on it. He checks out version 29, thus making a new version - version 30. Then another developer may come along and need to do something else to the script. The second developer will check out version 29 of the script and his new version of the script will be version 29.1.1
If you understand that, you truly are a God..