Rif.: Interactive Execution surprise

[ADagli · Accepted solution]

Hi Wolfgang,

sorry for letting you wait.

we were working and searching for an answer to your question. You see, we do not forget our customers 😉

What happend in the last days:

So far we forwarded this issue to our R&D department and they could reproduce this behaviour. But, they could not give me more information at the moment.

Therefore, we created a so called CAR (Corrective Active Request) with the number #371711.

R&D is working on it. If I get any information I will let you know. Otherwise you can contact NI again and ask for the actual status of this CAR.

Also, with the releases and updates of CVI, there always comes a readme-file where all the CARs which have been reported and successfully solved are listed.

So if there is any new update or release, please have a look into the readme. If you can see this number, also your request has been successfully implemented.

Best regards,

[Wolfgang]

---

ADagli wrote:You see, we do not forget our customers 😉

---

Thanks! Indeed NI's support is one of the strongest assets of CVI...

[D_Biel]

I also wanted to add that DebugPrintf does not report this error.

[Edit]: Actually, DebugPrintf does report the error on first run. It seems to be more related to the #include as Wolfgang pointed out earlier.

[ADagli]

Hi @ all,

I wanted to inform you, that our R&D Department will solve this ussue with the next release LabWindows/CVI 2012 SP1.

Thank you all for your help and collaboration.

Best regards,