There is no simple right or wrong; it all depends on what you want to do. TIMTOWTDI and all that.
But, for standard use, please x $bignum, pretty please three times with a cherry on top, don't use GetObject or anything else that takes over an existing copy of Excel, Word or anything else. You don't know why I have opened it. It might be running a macro that will not stop for several days. It might become available at a critical point during a process when user input is required but the user is tearing a piece of paper off the end of a roll. It might have all sorts of strange options set because the user is developing something interesting. I could go on, but I'm sure you get the message. Open your own instance of Excel. If that means that two instances are open, that's fine. I do it all the time, and not just for automation purposes. It's built to take it. On the rare occasions that I use Excel 2013, it seems slow to me, too. That may not be a function of automation, let alone the invocation process. There are all sorts of tricks you can play to speed up automation such as preventing screen updating, recalculation, event handlers and the like. But that's an Excel subject rather than a Perl one.
Regards,
John Davies
In reply to Re: Win32-OLE: What is the canonical way to open file for editing?
by davies
in thread Win32-OLE: What is the canonical way to open file for editing?
by woland99
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |