It would be awesome if the DQMH validation tool could go back more than one version.
eg. If you open an old piece of code (that was written in say DQMH 4.2), the only way to upgrade it to 6.1 is to one version at a time, upgrade the code step by step. This would mean the following:
- Install DQMH 5.
- Run Validation tool
- Install DQMH 6
- Run Validation tool
- Install DQMH 6.1
- Run Validation tool
This is a rather painful process, and when faced with this, I have decided to simply implement the module again starting from the latest version, and porting the code over rather than go through that.
Neither approach is obviously ideal.
We really need a tool that can convert an older module up to the latest standard. This will become a more common problem now that we have DQMH-based code out there from 2018 onwards. The more people use it, the more this problem will surface.
Christopher Farmer
Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au
Hi @Ozfarmboy
As discussed during the last TA meeting, we are declining your request because the validator should support this as is.
For the record, any case where it does not is a bug that needs to be reported and fixed.
Support starts at v3.0.
Thanks for your contribution and let us know if you have any trouble when validating your DQMH modules 😉