missing config functions in 2009

[falkpl]

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.

[Darin.K · Accepted solution]

Check this out.

http://forums.ni.com/ni/board/message?board.id=features&thread.id=429&view=by_date_ascending&page=1 

[falkpl]

Thanks I saw the pros and cons of NI decision to make some functionality private but this still breaks my code.  What is the best solution it is not all that clear (maybe after sleep it might be clearer).  Should I add the code from an older version of labview to my code?  What would the designers of the library say to do.  I dont want to rewrite my code at a higher level that is too expensive for this application.

[falkpl]

If the rules change on new versions of LV, there should be (I cant find one) an app note on dealing with this.

Message Edited by falkpl on 01-15-2010 08:47 AM

[NAKeel]

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.

[falkpl]

Thanks this is what I ended up doing, I wasent sure if the was an 'best practices' here or not.