VBA Compatibility between MS 2007, 2010

[Beatrice]

I have a series of excel files run with some VBA code. It works fine on few computers and we found out one of our colleagues could not execute the “export button”. Her version was MS 2010, while the files were created with MS 2007. (The strangest part : we have computers with MS 2010 also can proceed the files without problems)

I would if there is anyone face the same issue before? any hint due to the MS version? Just curious as VBA code should work the same across different versions indeed... ?

Thanks in advance

 

[Norie]

It might not be a compatibility issue.

How is the code not working for the user?

Are they getting errors?

 

[Beatrice]

There is no response after the mouse click. Those buttons were created by [forms control] under the [developer] tab.
we checked the excel [file] options settings are same as the one which executed just fine.
That’s why I am a bit puzzled.

 

[Norie]

What exactly is happening?

Are they able to open the file with no problem?

What are they clicking?

If its buttons have you checked the correct macros are assigned to those buttons?

 

[Beatrice]

To describe the situation, these excel files are saved in server and at the moment we have 4 users. 3 of us run the files without problems, but one of us is able to open and use the files, but can’t activate the “export button” (form controls VBA) as other user

 

[Fluff]

Are there other macros in that workbook?
If so can the user with problems run those macros?

 

[Beatrice]

Are there other macros in that workbook?
If so can the user with problems run those macros?

Indeed each file contains quite a few macros, she didn’t report any error apart from that, so I guess the rest of the macros run fine. I will check again with her when back to office tomorrow.
I will also send her a new file for a simple test run to ensure her computer is running macros.
Thanks for the hint.

 

[Fluff]

Hopefully it will be that simple, let us know how it goes.

 

[Norie]

If they can't, or seem to be unable to, activate the button then I would definitely check if the correct macro is assigned to it.

That can easily be done by right clicking the button and selecting Assign macro...

If the correct macro is assigned to the button I would suggest moving on to finding out what's happening then that macro is triggered.

You can easily do that by adding a breakpoint to the macro with F9, pressing the button and then stepping through the code with F8.

 

[Beatrice]

Hopefully it will be that simple, let us know how it goes.

Well apparently not that simple ?

According to our IT team, there is a conflict between a certain window update/discontinued support and MS office. So we have to purchase new office 365 licences. Let’s see if this will solve the issue.