That's been my experience. I don't make the object visible until it's ready for presentation to the end user. But if an error occurs during processing and gets trapped by the try..catch, I can make sure the user is notified and make the COM object visible at the point where no more processing is happening.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: Sunday, October 23, 2016 3:16 PM To: profoxtech@leafe.com Subject: RE: Excel errors
On 2016-10-21 18:28, Richard Kaye wrote:
That's become a standard part of my exception handling with COM stuff. If I catch any kind of error, I check to see if the Word or Excel object is in scope and make it visible.
Understandable, but the processing runs faster if it's invisible, right?