Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Problems with VFP and Excel 2000?...
Message
From
23/12/1999 14:31:18
 
 
To
23/12/1999 14:18:41
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Miscellaneous
Thread ID:
00308023
Message ID:
00308131
Views:
39
>Ditto on NT4. Curious that oExcel = .NULL would get rid of it completely. I mean, that's good but you would think an explicit quit would work.

Why would it? Wouldn't this be like leaving a variable reference to an object around, the object doesn't go away until the reference is cleared? Seems logical to me, given the way VFP works with objects.


>
>
>
>>>That's what I was afraid of. As I mentioned in my post (^&$$%@ HTML tags< g >), I used both oExcel = NULL and RELEASE oExcel, just to be sure with no affect. I would hope that someone (preferably running Win 98 SE) would confirm this though, even if I'm already pretty sure of the answer.
>>>
>>
>>
>>Don't have an SE machine but just tried on a Win98 machine, and my results were consistent with Bill's:
>>
>>.Quit leaves the program running.
>>
>>oXL = .NULL.
>>
>>gets rif of it completely.
Fred
Microsoft Visual FoxPro MVP

foxcentral.net
Previous
Reply
Map
View

Click here to load this message in the networking platform