Different VBA versions matter?

[krag]

I am working between 2 PCs, one is with VBA 7.1.1042 (Japanese Win 7, Access 2013)


Other is VBA 7.1.1038 (English Win 7, Access 2013)
VBA program made on 1038 version ran OK in 1042.
But other way round, from 1042 to 1038, error message that macro or event procedure is not recognized.
In design view, there is no problem to open the modules from the form.
Anybody had similar issue?
I suspect version number matters and unable to figure out how to update the version from 1038 to 1042.

[ranman256]

Not that I've used different languages of Access, BUT, I get errors due VBA hitting an exotic object.
One was an email .dll that didnt exist on the other PC. This gives false errors in the code..like: "RIGHT(word,1) is not a function." Bull#@%, Because it is.
So check the vba, TOOLS, REFERENCES, and make sure no items are MISSING.

[krag]

I have checked for any missing items but all seems ok.
I have to test run the program in debug mode again and see if it really is executing from event procedure.
Perhaps it is not recognizing the event procedure due to language.
Tks for yr advice anyhow.

[krag]

With debug mode, I found out today that the database is not even opening the VBA program and stopping with the message as attached.
This message is same with any of the on-click event procedures in the form.
I am unable to figure out the relation of OLE server or active X control mentioned in the message.
Hope some one can help me out to get over this problem.
I have asked my partner working on the english version to try update the active X control and see if it resolves the issue.

[hapm]

Tried to recompile the modules using the vba editor?