As it turns out, my dirty solution of ignoring the error#1 did not solve all problems when shutting down Windows, and other situations. I gave up completely on using Excel API stuff. Since I was using no calculations, I re-coded all VIs to use reading tab-delimited text files into a multi-column listbox and to use several VIs I coded last year to get/change values (and attributes) in those "cells" instead. Works like a charm. No more "Excel has caused an error" messages. No more concerns about whether using Excel API requires licensing Excel, etc. Simple, no more Excel! This worked great also, BTW, for no longer using Microsoft's flexgrid controls and its associated API/COM crap in my front panel(s). Using multi-column listboxes, I found, is much prettier
and just as fast for GUI displays. I feel much better now, no API's except for ones used by LabVIEW and TestStand. No more DCOM/Registy headaches. Only have to use NI's products greatly simplifies my life!
