Page 1 of 1

Error in "GET XLS DATA" when I run a model that previously worked fine

Posted: Wed Oct 16, 2019 5:15 pm
by ashiish
I am using Vensim PLE Plus ver 6.2 (x32) on Windows. I have had a model saved for many years and it worked fine earlier (I last tried it about a year ago).

When I run it today, I get the error "ERROR: Failed to connect to Excel to get data from <filename>.xls".

The .mdl file and the .xls file are in the same directory.

Re: Error in "GET XLS DATA" when I run a model that previously worked fine

Posted: Thu Oct 17, 2019 2:15 am
by tomfid
I've had the same problem recently on 1 out of 3 systems. I think it may be an Excel change. Switching from GET XLS to GET DIRECT may help.

Re: Error in "GET XLS DATA" when I run a model that previously worked fine

Posted: Thu Oct 17, 2019 4:39 pm
by ashiish
MANY thanks. That worked.

I had to manually replace the GET XLSes with GET DIRECTs in about a 100 places though. Is there an easy way to do that?

Re: Error in "GET XLS DATA" when I run a model that previously worked fine

Posted: Thu Oct 17, 2019 4:49 pm
by Administrator
If you edit the settings in vensim, there should be an option to change the protocol used in getting values from ole to direct. This makes vensim use the direct method for everything.

Re: Error in "GET XLS DATA" when I run a model that previously worked fine

Posted: Thu Oct 17, 2019 4:49 pm
by tomfid
You can switch to text view (View>As Text) and use the search & replace (Edit>Replace String). Or, save the model to mdl and use your favorite text editor (Notepad++ is good and free).

Re: Error in "GET XLS DATA" when I run a model that previously worked fine

Posted: Thu Oct 17, 2019 4:51 pm
by Administrator
Ps. Can you share the original model and excel file so I can test to see why OLE is not working to get the values? If not on the forum, you can email vensim@vensim.com.

Re: Error in "GET XLS DATA" when I run a model that previously worked fine

Posted: Mon Oct 28, 2019 8:00 pm
by tomfid
This is fixed in 8.0.6. The problem appears to be Microsoft changes for OneDrive/Sharepoint integration.