Excel 2013 VBA Code not Backwards compatible with Excel 2010

As mentioned, missing references/libraries can usually be corrected.

Its also possible to write the code using late binding instead of early binding, which usually is a better approach when in a mixed environment.

Also, VBA (and code in general) is not one size fits all. Just because it works in 1 version (or even subversion) does not mean it will work in another. The only sure fire way to ensure it works in all versions being used is to test it and make adjustments until it works in all versions.

I find in situations where my code is:

• Complex
• Used accross multiple versions

That it benefits me to write my code as modular as possible. By doing so its easier to adjust or replace small segments of code when the need arises instead of digging through a huge module of code.

It sounds like you have some troubleshooting ahead of you.