I was wondering if anyone else could shed some light on this problem (it's got tech support stumped).
To date I have two build machines and three target machines that have had the same problem. I build a DLL in LabVIEW that contains the Easy Text Report vi. I also create a VI that calls this DLL function to test it out. Everything works fine on my build machines. On my target machines, however...
On the target machine I put a call library function node on the block diagram and configure it for the LabVIEW DLL I created, select the function and setup the parameters to the function. Upon clicking on OK on the configuration window for the call library function node, my hard drive access spikes for some period of time (sometimes fractions of seconds, sometimes seconds); I assume the VI inside the DLL is being loaded into memory. I then get a Windows message stating that LabVIEW needs to be shut down at which point Windows terminates LabVIEW. Removing the Easy Text Report from the DLL VI eliminates the crash. Tech support has helped narrow this down a bit -- it seems to specifically be the print portion of the report generation VIs (they sent me a DLL that creates an HTML report which had no issues).
I'm doing this in LabVIEW 8.0. To make things more interesting, I have the same code in LabVIEW 7.0 and 7.1; neither of these have any problems. I've attached the code (LabVIEW 8.0) that tech support and I have been messing with.
Any thoughts or sugestions?
Tim Stahl
