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:[email protected]] On Behalf Of [email protected] Sent: Sunday, October 23, 2016 3:16 PM To: [email protected] 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? _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/bn4pr10mb0913cca0cd60385227f66ee3d2...@bn4pr10mb0913.namprd10.prod.outlook.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
