XL Ole Automation

[mkane53]

I'm having trouble with OLE automation from FoxPro 5.0 I'm able to launch, manipulate, save, etc. the xls spreadsheet just fine. However, even though I use the oxlApp.quit() and then release the object, it's still showing that it's running in the background.

I'm using Win20000 and with each iteration, it creates a new incidence of Excel.exe; Running the same code using Fox 7.0 doesn't show the same problem, but my client doesn't want me to upgrade them to the Fox 7.0 runtimes just yet.

Any suggestions would be greatly apprecidated

 

[rgbean]

While I don't have the answer you want, you might want to suggest that the VFP 5.0 app will work if they go back to Excel 95. With Excel 2000 they need VFP 6.0 and Excel 2002 they need VFP 7.0! <g> [Not really, but while they are thinking about that, maybe you can come up with a &quot;real&quot; answer.]

Are you using:
oleApp = GETOBJECT(, &quot;Excel.Application&quot
to start up subsequent Excel sessions?

Rick

 

[mkane53]

Thanks Rick. Yep, I've used VFPs GetObject() function, but I assume because I've already released the object, it doesn't find it in memory and simple creates another instance. Probably the client's just going to have to bite the bullet and let me upgrade the dlls to the Fox 6.0 runtimes and I'll re-compile in 6.0 and see what happens.

Thanks for the info and for your help