01-14-2010 08:29 PM
I am missing some config functions after upgrading legacy code to 2009.
Specifically "config data registry function.clt" and config data registry.vi"
what is the best way to handle this (copy and rename old lib functions???"
Why would ni break old code on an upgrade by removing public functionality.
Solved! Go to Solution.
01-14-2010 08:38 PM
01-14-2010 10:09 PM
01-15-2010 07:46 AM - edited 01-15-2010 07:47 AM
If the rules change on new versions of LV, there should be (I cant find one) an app note on dealing with this.
01-15-2010 09:34 AM
Hi Paul,
I pulled this from the attached forum, but I think it answers your question:
"If a customer want to use any of its subVIs, he has to keep a copy of the subVI, and maintain the copy himself in the future. It losts the upgradeability. But it guarantees an application works on the future LabVIEW version. For most customers, keep their application work is the most important thing, have better performance is the second."
Upgrading the VIs those VIs yourself and using them should work for you. Please repost if you run into problems.
01-15-2010 09:37 AM
Thanks this is what I ended up doing, I wasent sure if the was an 'best practices' here or not.