This could work in some situations, but in most I need to have Excel instantiated because I populate the worksheet as I scan the cursor.
Thanks anyways El 14/06/2010 11:50, Kurt Wendt escribió: > Rafael - I understand your predicament - as I have also done some Excel > Automation recently. > > Maybe this suggestion sounds simplistic - but, why not do your data > manipulation (cursor creation and such) BEFORE you actually create the > Excel Object. This way - if an error occurs - you haven't already done > the Excel stuff - and therefore have not affected Excel and caused it to > be Invisible. > > HTH, > -K- > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Rafael Copquin > Sent: Monday, June 14, 2010 10:37 AM > > I read Microsoft Office Automation with Visual FoxPro by Tamar Grainor > and others, ages ago, and it has been very useful to me over the years. > > However, there is something I could never get to work and it is this: > > suppose that for some reason an error occurs in your application while > the Excel object has been instantiated and the worksheet is not > visible... > > TIA > > Rafael Copquin > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** 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.
