topic Re: vlax-get-object creates new Excel instance even when a workbook is open in Visual LISP, AutoLISP and General Customization Forum

vlax-get-object creates new Excel instance even when a workbook is open

deheylen — Mon, 10 Feb 2020 18:13:55 GMT

I am trying to retrieve the current selection from an open excel workbook. When I run this code:

(setq ^ExcelApp (vlax-get-object "Excel.Application"))

it creates a new, empty instance of excel even though there is already one running. I'm using AutoCAD MEP 2018 and Excel 2010. Is this a bug in VisualLisp or am I doing something wrong? If it's a bug are there any workarounds?

Thanks for any help that can be offered with this.

Re: vlax-get-object creates new Excel instance even when a workbook is open

ronjonp — Mon, 10 Feb 2020 18:31:10 GMT

Have you tried this?

(setq ^ExcelApp (vlax-get-or-create-object "Excel.Application"))

Re: vlax-get-object creates new Excel instance even when a workbook is open

deheylen — Mon, 10 Feb 2020 20:45:02 GMT

I did try that and I get the same result: a new instance of Excel is created rather than linking to the existing instance.

Re: vlax-get-object creates new Excel instance even when a workbook is open

Sea-Haven — Tue, 11 Feb 2020 05:09:41 GMT

Have a look at the start of this code. its a bit long winded many lines not just a couple.

Re: vlax-get-object creates new Excel instance even when a workbook is open

ronjonp — Tue, 11 Feb 2020 15:47:00 GMT

@deheylen wrote:
I did try that and I get the same result: a new instance of Excel is created rather than linking to the existing instance.

I cannot replicate this .. I'm also on 2016 version though.

Re: vlax-get-object creates new Excel instance even when a workbook is open

Anonymous — Thu, 03 Sep 2020 16:06:52 GMT

Did you ever find a solution to this? I'm having the same issue on a specific machine. vlax-get-or-create-object ends up creating a new Excel.Application object instead of getting the current one. Both machines are running Office 365 but behave differently. The only difference is, one runs ACAD 2018, and the problematic one runs ACAD 2020.

Re: vlax-get-object creates new Excel instance even when a workbook is open

Sea-Haven — Fri, 04 Sep 2020 05:00:23 GMT

I had some other code and it did a check is excel open if not open it will try to find its a variation on the

(setq *ExcelApp% (vlax-get-or-create-object "Excel.Application"))

: (setq excel-app (vlax-get-or-create-object "excel.application") (_> wb-collection (vlax-get excel-app "workbooks")) #<VLA-OBJECT Workbooks 0000000023950548> : (vlax-dump-object wb-collection) ; Workbooks 23950548 : ; Property values : ; Application (RO) = #<VLA-OBJECT _Application 0000000023951268> ; Count (RO) = 1 Count will be 0 if no excel open but if no workbooks also may return same value. Nil names. So a double check count /=0 and wb not "" (vlax-for wb wb-collection (princ (vla-get-fullname wb)) )

Re: vlax-get-object creates new Excel instance even when a workbook is open

MrJSmith — Tue, 19 Jan 2021 19:46:28 GMT

I have run into the same issue. In the past, I could typically fix it by restarting my computer (I tend to leave it on for weeks at a time.) However, it seems that won't fix the issue anymore with the latest version of Office 365. Autocad now seems unable to detect that Excel is indeed open when not opening Excel via VLAX commands.

This makes it impossible to handle Excel files in an orderly fashion through AutoCAD visual commands and completely ruins many of my Excel handling scripts (or at least requires the user to close all Excel files before running the scripts.)

There might be some Microsoft excel security feature that is blocking the information?