Hello,
I have started to have an older problem "escalated". I had a previous post about a dll which is playing an interface role between a program running under Windows, and LabView. The details are here:
Note that, this is not a duplicate post, I just mentioned my recent problem there, when it was not that frequent.
Today -reason unknown- after a win system restart I cannot run my LabView code from the development environment. When I run the main VI, it crashes the whole LabView environment at the first dll call. This problem we had before too, but at the 2nd of 3rd try it ran OK. Today I tried like 30 times, also did many system restart. The native spectroscope software runs fine also.
Strange enough, if I run the build exe, everything works fine. The problem appears only when I run from LabView. There is no error code, only a window appeared at the first time, like I can send the error report to NI. I can dig into some log files tomorrow at the lab, I just need to know where I can look for it.
It looks like someone else also experienced similar behavior with external dll calling:
http://forums.ni.com/t5/LabVIEW/Problem-Dll-crashes-LabVIEW/m-p/2562667/highlight/true#M773565
"In the resulting application (Exe) it seems to work fine."
What is the difference between when the dll is built into the exe, and when it is run from LabView dev environment?
Thanks for any idea, and help!
(if nothing helps, I will just re-build the exe after program changes, but it slows down coding a bit :)
Last time we did not get feedback from the company who created this dll, I will try to contact again...)