asked on Word 2003 macro in Word 2016 "Run-time error '5'"
We have two macros that were written for Word 2003, but now have to upgrade to Word 2016 on a new Remote Desktop server. The macro shows up under the "Add-ins" tab but when we click it, we see the following error:
Microsoft Visual Basic
Run-time error '5':
Invalid procedure call or argument
Changing the Trust Center macro settings has no effect.
Is it possible to convert these macros to work in Word 2016? If so, how? If not, what are the next steps?
Microsoft Visual Basic
Run-time error '5':
Invalid procedure call or argument
Changing the Trust Center macro settings has no effect.
Is it possible to convert these macros to work in Word 2016? If so, how? If not, what are the next steps?
VBAMicrosoft WordDesktops
Last Comment
Ramin
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Here's the subroutine of the smaller of the two macros:
If I delete the subroutine, the macro will run (but of course it won't work properly).
I don't have any experience of macros or VBA. Could you give me a suggestion how to amend this code? Many thanks.
Sub GetPrintername(CurPrinter)
CurPrinter = Application.ActivePrinter
WordInStr = InStr(1, CurPrinter, " on ", vbTextCompare)
CurPrinter = Mid$(CurPrinter, 1, WordInStr - 1)
End Sub
If I delete the subroutine, the macro will run (but of course it won't work properly).
I don't have any experience of macros or VBA. Could you give me a suggestion how to amend this code? Many thanks.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Fantastic, the macro now runs! Also made the same change in the larger of the two. Thanks very much! We are testing it now. Will post outcome in due course.
ASKER
Yes, this works now, There is a different problem regarding the behaviour of the macro, but that's a different story. Will ask another question if necessary. Thanks again!
You're welcome, I'm glad it works.
this error could be machine specified and probably inherited from Word 2003?