Hi,
Recently I changed computer - now Windows 11. Clarion 11.0.1360
Every time I try to use EasyExcel it trows an error:
(Means: error during loading) - The demo app does that too…
Does anyone know if that can be fixed?
Thanks, Piet Bouma
Hi,
Recently I changed computer - now Windows 11. Clarion 11.0.1360
Every time I try to use EasyExcel it trows an error:
Hi Piet,
Maybe this is the problem:
EasyExcel supports all Excel version that support COM automation (NOT starter, student or home version ).
Dank je Rob,
I use Office 365.
In an email from Guennadi (Ingasoftplus): (a few years ago…)
“EasyExcel doesn’t work with Office 365 because Office 365 doesn’t support OLE automation”.
Guennadi,
But did some test on a Windows 10 computer with the same app and Office 365 and it works there.
Must have done a trick…once
As Rob and you said. Also are you sure that you have Excel installed correctly?
Yes I did. I do not want to be unfriendly but why does EasyExcel not work with Office 365. I think this is used by a lot of folks.
But the trick: I installed an older version of msVisio (2013) and EE works…turns out I’ve done this before
odd? yes do I understand it ? no
It works just fine. just checked it:
Probably it turns On some automation so Excel gets this setting too…
I just ran into a similar problem on my dev machine. The app loads but any commands to Excel produce: “Error loading type library/DLL.”
Using C10. I’m not sure where a person can get an old version of msVisio (2013) – if that, in fact, is the cure.
Suggestions?
Thanks.
Jim
I dont know if this is relevant, but it might be worth look at the COM TLib versions.
Excel 2007 was installed and it’s COM Classes are registered in HKCR\TypeLib{00020813-0000-0000-C000-000000000046}\1.6
call Excel through COM automation it used HKCR\TypeLib{00020813-0000-0000-C000-000000000046}\1.7.
was trying to talk to Excel 2010 instead which was not present.
This might also be relevant
Looks like Registry TLib issues in both cases, which will probably explain being able to install the msVisio (2013) to get things to work.
Thanks Rich. I’ll take a look. Appreciate the help.
I dont know if this is relevant, but it might be worth look at the COM TLib versions.
Excel 2007 was installed and it’s COM Classes are registered in HKCR\TypeLib{00020813-0000-0000-C000-000000000046}\1.6
call Excel through COM automation it used HKCR\TypeLib{00020813-0000-0000-C000-000000000046}\1.7.
was trying to talk to Excel 2010 instead which was not present.
This might also be relevant
https://learn.microsoft.com/en-us/answers/questions/4988544/solved-getting-error-in-loading-dll-messages-after?forum=msoffice-all&referrer=answers
Looks like Registry TLib issues in both cases, which will probably explain being able to install the msVisio (2013) to get things to work.