Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Releasing Excel
Message
From
11/05/2005 04:16:53
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
 
 
To
11/05/2005 04:09:49
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Title:
Environment versions
OS:
Windows XP
Miscellaneous
Thread ID:
01012715
Message ID:
01012742
Views:
21
>Hi Cetin
>
>Yes I am declaring another variable as oSheet=oExcel.ActiveSheet, but I am releasing the oSheet object before issuing the oExcel.quit and releasing the oExcel object. Is this the incorrect way to go about this? Or should I not be using the oSheet at all?
>
>Thanks
>Darren

Darren,
I almost never do that. It might be the point. I generally do like this:

with oExcel.ActiveWorkBook.ActiveSheet
.Something

vs
oSheet = oExcel.ActiveWorkBook.ActiveSheet
oSheet.Something

I can't say it's the incorrect way. Just not using like that and not having problems it comes to mind. Excel leaving open in processes suggests there is a hanging reference somewhere.
Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform