I've run into a situation that can't be unique. I was wondering if
anyone had worked out a good solution.
I wrote a program for a monitoring system that must run 24/7.
Actually an upgrade. The first system wrote reports in Word using
ActiveX. A bit of a struggle, but it all worked as I wanted since I
wrote it all. This time I got "smart" and used the Report Generator.
Works fine, most of the time. However, if anything goes wrong, the
Report Generator VI's have dialogs all over them for handling errors. So
when a file won't write, for whatever reason, my whole monitoring
program hangs until someone comes by (days later) and acknowledges the
dialog.
I've thought of two solutions:
1) Fix the condition that causes file errors in my program. (There's
a small bug that tries to write to the same "new" file twice. I could
get rid of that.) But that doesn't prevent other errors from hanging
the program.
2) Copy the Report Gen heirarchy and rewrite it to get rid of all
dialogs. Ugh...
Seems like there should be a more global, built-in solution. NI
toolkits should have some option or setting or front-panel control the
disables all dialogs and sends errors out to the calling VIs.
Anyone have any other ideas? How have you handled this?
Regards,
Dave
-------------------------------------------------------------
David Thomson 303-499-1973 (voice and fax)
Original Code Consulting dthomson@originalcode.com
www.originalcode.com
National Instruments Alliance Program Member
Certified LabVIEW Developer
Certified Instrument Driver Developer
-------------------------------------------------------------
Research Scientist 303-497-3470 (voice)
NOAA Aeronomy Laboratory 303-497-5373 (fax)
Boulder, Colorado David.S.Thomson@noaa.gov
-------------------------------------------------------------
There are 10 kinds of people: those who understand binary,
and those who don't.
