08-10-2016 12:23 PM
I've seen something like that before when upgrading from Office 2010 t0 Office 2013. The error is generated by the Excel Merge Cells.vi that is contained in the Excel Easy Text.vi. It seem that this only happens when the Excel window is minimized. The easy fix is to set the window state to anything but minimized in the New Report.vi.
Ben64
08-10-2016 01:33 PM
Ben,
That fixed the problem actually. I was minimizing it in my application. So can i not minimize excel now as a user or later in the program? Because if the user takes control of excel they can cause problems with the application correct? Also, does NI know about this problem? Seems like quite the bug to me.
08-10-2016 01:39 PM
matt198717 a écrit :Ben,
That fixed the problem actually. I was minimizing it in my application. So can i not minimize excel now as a user or later in the program? Because if the user takes control of excel they can cause problems with the application correct? Also, does NI know about this problem? Seems like quite the bug to me.
Even if minimized the user can take control of Excel, that's the risk of using Excel for report generation. I don't know if NI is aware of the issue but for me chances are the problem is on the Microsoft side. I observed the same problem with Office 2016.
Ben64
08-10-2016 01:43 PM
I know they can still take control if minimized, but less likely ha. Youre probably correct about that being microsoft as well. Do you know of a way to disable the user from taking control of excel?
08-10-2016 02:32 PM
matt198717 a écrit :I know they can still take control if minimized, but less likely ha. Youre probably correct about that being microsoft as well. Do you know of a way to disable the user from taking control of excel?
There were a few thread on the subject and for what I remember there was no solution to that (you can try a forum search on this topic). In my case the applications are for internal use so all the people likely to operate the software all well aware not to use Excel when a test is running. You can try setting the window state to nochange, if the file was close it should open minimized.
Ben64
Ben64
08-10-2016 04:12 PM
Thats a possibility. I guess ill have to look into it.
Thanks for the help.
08-11-2016 09:21 AM
I am just confirming this behavior of Office 2013/Excel creating an error when minimizing the window. I have an executable that was running fine since 2009. IT pushed out Excel 2013 and the app stopped working...the template would load and would write some header type information...I would then minimize the window which resulted in an undefined error. I did some research and I think it has something to do with Microsoft changing the design of the Excel UI window. I hope others read this thread so it saves them some troubleshooting time.
08-11-2016 10:17 AM
Bob,
I completely agree. I wasted a valuable day trying to debug the error, which had i known the problem it could have been fixed in 5 seconds.