02-06-2017 08:01 AM
Have a sequence that uses Excel to hold properties and test limits. The Test Sequence uses the Property Loader to load specific properties and test limts with respec to section names. A Run Time error is encountered when the property loader attempts to open an Excel Instance but the operator has an Excel worksheet open and a worksheet cell is active (menaing the operator is in the process of updating a value within a cell). Is there a TestStand option that cna ignore this RunTime error and open an Excel Worksheet even if a Worksheet Cell is active in a different Worksheet?
02-06-2017 01:55 PM
02-06-2017 02:49 PM
Hi Kevin,
I'm pretty sure this is a limitation of Excel and not one of TestStand or the Property Loader step. When you're editing a cell in Excel, you can't do anything else like open another file or create a new blank workbook from another instance of Excel, or do any file manipulation until you get out of the cell you are editing. I'm not 100% sure of this, but I think Excel is what's blocking the Property Loader step; it's not a feature of TestStand.
What you could do is check to see if the Property Loader step errored, and if so, prompt the user to complete their edits before continuing. Then swallow the error and retry the Property Loader operation.
Hope this helps!
-Jack