Weird issues with LV2009 when downgrading project version

[LVexpert2b]

Hello Folks,

I am having a weird issues with LV2009.

One of my projects that was working fine in LV8.6, has  broken arrows in LV2009 when I ported it over.

Upon further investigation, I found that under ...\LabVIEW 8.6\vi.lib\Utility\config.llb doesn't  exist in LV2009 as an LLB but as regular directory.

Furthermore, some of the VIs that were in the config.llb aren't even in the config.llb folder.

I realized that NI completely changed the iner workings of "Configuration File VIs" [they are using queues instead of File refnums!]

Although, I realized I how I can get most of the code working by type-casting the File refnums with a queue refnum] but modifiying the code is currently not option and one file "Config Data Write To File.vi" (which is in config.llb) is still missing from LV2009.

Hence, I had no choice but to down grade back to LV8.6.

However, after saving the project from 2009 to 8.6, LabVIEW always says that changes were made to a few of the VIs if opened within the project or inidividually even if no changes were done.

The change details state "Disable structure switched frame". I did have Disable Diagram structure in those VIs but I deleted them.

I searched the forums for "Disable structure switched frame" but got no results.

Anybody experienced this problem or have any suggestions?

Thanks in advance.

LVexpert2b

CLD

[A_Person]

It would appear that this is related to a reported CAR #147367.  I will have to get a little more information on this and I will let you know what I find.

[LVexpert2b]

Hi Alex,

Any info on that CAR yet? 

I also wanted to know if the CAR is for the changes in config.llb or for the  "Disable structure switched frame" when downgrading from LV2009.

Thanks

[Ben]

---

A Person wrote:
It would appear that this is related to a reported CAR #147367.  I will have to get a little more information on this and I will let you know what I find.

---

Please update us on this issue.

Ben

[DFGray]

The CAR relates to the "Disable structure switched frame".  It fixes a bug that you always get a dirty dot, even when you have saved.  This CAR was marked fixed March 3, 2009, so it shipped with LabVIEW 2009.  The bug may be present in earlier versions of LabVIEW, as you experienced.

I suspect the issues with the configuration file VIs stem from using VIs which are not on the palette.  The palette is currently the official interface to anything.  Any VI not on the palette is not guaranteed to be present or compatible in future versions of LabVIEW (and yes, I have been bit by this).  The configuration file VIs were completely refactored to increase efficiency and speed.  Not surprisingly, the underlying structure changed.  That is what you are seeing.

There is a long thread on whether or not all VIs in vi.lib should be supported forever here.  If you have an opinion, please go there and state it.

[LVexpert2b]

Hi DFGray,

Where did you get the details of the CAR?

I tried searching on ni.com but I didn't get any results unlink other CARs.

I never had this dirty dot problem in LV86. This only shows up when downgrading from LV2009.

Any suggestion?

Thanks

[Ben]

---

DFGray wrote:

...

There is a long thread on whether or not all VIs in vi.lib should be supported forever here.  If you have an opinion, please go there and state it.

---

[Set Rant_Mode = True] 

I already did but I'll say it agin here.

... 

Long wicked rant removed prior to posting.

... 

Where did I leave my antacid?

[Set Rant_Mode = False]

Ben

I did reply to that thread and got no reply. I don't like this NEW rule about not using VIs in VI.lib.

[A_Person]

He got the information from our internal CAR database view.  I'm not clear on why you are seeing the dirty dot problem at this point.  It's possible that something in the downgrade caused it.  Either way, the root cause should be fixed for 2009 but obviously isn't going to do much for your 8.6 program.

Message Edited by A Person on 10-20-2009 02:57 PM

[LVexpert2b]

I didn't know that DFGray had access to NI's internal CAR database.

Is this accessisble to anyone?

With regards to the dirty dot, as I mentioned the problem was non existent in LV86.

This is not a major problem except that with SCC it is a nightmare!!!!!!!

I would like to move to LV2009 to avoid this problem however, the issue of the config.llb popped on me.

Hence, I am damned eitherway. Does this mean I have no other option?

Thanks

[Ben]

---

LVexpert2b wrote:

I didn't know that DFGray had access to NI's internal CAR database.

Is this accessisble to anyone?

...

---

Dr. Gray is NI.

I have been asking for four years to get access to the internal bug DB and was scared off because it contains both bugs in the public domain but also bugs in the yet to be released versions.

The Known Issues docs as well as the Bug list we mainatin in the breakpoint are the first palces to check. After that, a call to NI tech support can help.

Ben