Skip to main content

Rumba 9.4 & Office 2013 VBA 7.1 Compatibility

  • January 24, 2017
  • 16 replies
  • 0 views
D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba

16 replies

D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba

Hi Michael,

Currently we don't support EHLAPI from 64-bit process as the EHLAPI32.dll will not load inside 64-bit app.

Few options on your end:

1. Install Office in 32-bit mode as recommended by Microsoft - see technet.microsoft.com/.../ee681792.aspx

2. Wait for Rumba 9.5 release, coming in two weeks Feb 24, this release is supporting EHLAPI from 64-bit script / VBA processes - I assume a minor change to your script will be needed, mostly around initialization part.

We might be able to send you eval of 9.5 to play with :-)

Let me know if you have any more questions.

Thanks

Adi

D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba
Hi Adi!

Thank you for responding to my email. it appears my organization is considering option #1, but i believe option #2 is very interesting. I didn't know a new version was upcoming. This is very nice to hear especially since EHLAPI is going to be upgraded. Please do keep me posted regarding this.

p.s. An eval will be awesome!

Michael G.
D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba
Hi Michael,

I'm the product manager of Rumba. We are releasing Rumba 9.5 by the end of this month.

We also release a VBA add-on which will allow you to create and run VBA scripts from Rumba and MS Office.

Please get in touch with support to send you a pre-release eval version if you can't wait the end of this month.

Regards,

Dorian
D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba
Hi Michael,

I'm the product manager of Rumba. We are releasing Rumba 9.5 by the end of this month.

We also release a VBA add-on which will allow you to create and run VBA scripts from Rumba and MS Office.

Please get in touch with support to send you a pre-release eval version if you can't wait the end of this month.

Regards,

Dorian
D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba
Hi Michael,

I'm the product manager of Rumba. We are releasing Rumba 9.5 by the end of this month.

We also release a VBA add-on which will allow you to create and run VBA scripts from Rumba and MS Office.

Please get in touch with support to send you a pre-release eval version if you can't wait the end of this month.

Regards,

Dorian
D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba
Hi Dorian!

Thank you for your response. The release of a new product is always a very exciting time for everybody and I simply could not wait to go see what Rumba 9.5 can offer my company. I will ask support for an evaluation copy and hopefully they will be able to send me a copy soon.

Michael G.
D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba
Hi Michael,
The latest 9.5 release can be downloaded here:
www.microfocus.com/.../
Let us know if you need more help

Regards,

Adi
D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba
Hello Adi!

My organization is looking to upgrade again, this time to Microsoft Office 2016. If we are keeping Rumba version 9.4, can you tell me if we will encounter compatibility issues with Office 2016 for 32-bit and 64-bit architectures? Thanks in advance.

Michael G.
D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba
Hello Adi!

My organization is looking to upgrade again, this time to Microsoft Office 2016. If we are keeping Rumba version 9.4, can you tell me if we will encounter compatibility issues with Office 2016 for 32-bit and 64-bit architectures? Thanks in advance.

Michael G.
D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba

Hi Michael,

as Adi has indicated there are issues with 64 bit MS office loading 32 bit .dlls
More details at: https://msdn.microsoft.com/en-us/library/ee691831(office.14).aspx#odc_office2010_Compatibility32bit64bit_Comparing32BitSystemsto64BitSystems 

Personally I'd stick with 32bit MS Office, however if you need to install 64 bit Office then you should use the MS Office code compatibility inspector: https://technet.microsoft.com/en-us/library/ee833946(office.14).aspx 

Hopefully adding VBA7 style declarations (if an "If VBA7 then ..else ... End If" block) in your VBA will suffice, if not then you need to consider a move to RUMBA 9.5 for official support.

Tom

D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba
Hi Michael,

I can only add that we are releasing a newer VBA version under Rumba 9.5 SP1 coming early November with many new and improved VBA features.

I do recommend looking into Rumba 9.5 as it built for automation in mind.

Thanks
Adi
D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba
Hi Adi - I've sent an email just now to customercare as well as posted elsewhere in this forum. Is it possible to used DDE to communicate with Rumba 9.4.1? Specifically, I would like to send keystrokes and retrieve text from the screen. I believe I need a list of the DDE items that Rumba recognizes - any examples would be appreciated.
D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba
Dorian. I am testing RUMBA 9.5 as a replacement for version 7. The ability to run my VBA scripts is crucial How can I get the evaluation of the ADD-ON for using VBA scripts ?

Thanks!

Edgar
D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba
Dorian. I am testing RUMBA 9.5 as a replacement for version 7. The ability to run my VBA scripts is crucial How can I get the evaluation of the ADD-ON for using VBA scripts ?

Thanks!

Edgar
André Escudero

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba

emelecio,

if you already have Rumba VBA Scripts (*.csf) then take a look at the downloaded Rumba package.
You should have a ScriptEngine.msi. This msi installs the VBA Script Engine that you know from RUMBA 7.


However with RUMBA 9.5 we have a new VBA Add-on,it provides the ability to create macros using Microsoft Visual Basic for Applications (VBA). 
The new VBA Addon for RUMBA 9.5 makes it easier to automate RUMBA from Excel and other third-party Applications.

See below screenshot: No 1: Shows the classic Rumba Script Engine. No 2 shows  the new VBA Addon.

 

 

 Let me know if you need the new VBA Add-on.

 

 

D

Hello Everybody!

My organization is preparing to upgrade to Windows 10 64-bit, Office 2013 64-bit, and Rumba 9.4. I've been tasked to check VBA macro compatibility between these platforms before the big jump, and I've encountered my first big wall. It appears VBA is no longer able to read EHLAPI32.DLL declarations that we use to start our legacy macros, saying that the DLL file does not exist despite it being at the specified location. We have several dozen macros that work fine for Office 2010 and Rumba 8, but all are potentially rendered unusable if we proceed with the upgrade. Has anyone found a workaround for this? Any suggestions or recommendations will be very much appreciated. 

Michael G.


#Office2013
#EHLAPI32.DLL
#Rumba9.4
#Rumba

Looks like a similar issue I was faced previously by my organisation. I have no longer find the perfect answer. Now, I hope this post will give the best solution to my problem. Many sites like EOT company in London are not opening properly.

Recent badge winners

Explore all badges
Terms & ConditionsAccessibility statement