Repair Word 2013 Automation Macro
Budget: $30 – $250 AUD
I have a macro that someone else wrote and was unable to get it to run on my version of Word. (2013)
I need it debugged.
This is a macro to assist in writing play scripts.
The process is
Assign a title
Assign a number of acts.
Name the characters and describe them.
Assign a scene
Assign props (A prop is anything on stage that is moved or used by an actor)
(During the writing process further scenes characters and props can be added)
Then when the writing process begins I use a hot key to start writing what each character says
e.g. if I want to write this dialogue between Joe and Karen
JOE {insert TAB here} You really are very annoying!
KAREN {insert TAB here} What have I done this time? (She moves stage right and picks up a book)
JOE {insert TAB here} If you don't know, I am not going to tell you!
This would end up looking like the image below. The stuff in italics is a stage direction.
To write this I need hotkeys assigned to each character so that it writes the name and inserts a TAB.
I am not sure what keys to use, FN CTRL or ALT but in this example ALT K could be assigned to the KAREN character.
I need to occasionally change the look ( font, spacing tabs etc).
I need to print it out in booklet form.
I need to print it out in actor form. This prints in 14 point font with the name and dialogue of just one actor in BOLD. (To help actors memorise their role)
Each page should have Copyright Paul Hannah and the current year as a footer.
Finally I need to import my current plays so I can revise them.
• Review the existing code, pinpoint whatever changed in the Word 2013 object model or security settings, and remove the blockers.
• Restore every shortcut-key assignment and formatting behaviour so the macro once again automates those repetitive tasks seamlessly.
• Return a clean, commented macro that loads without Trust Center complaints and works on any fresh Word 2013 install.
If the fix requires minor refactoring or a module split, that’s fine—just keep the workflow identical from the user’s perspective. Once your updated macro passes a quick acceptance test (all key mappings fire, formatting looks right, and no errors appear), the job is complete.
This is the error that comes up.
I need it debugged.
This is a macro to assist in writing play scripts.
The process is
Assign a title
Assign a number of acts.
Name the characters and describe them.
Assign a scene
Assign props (A prop is anything on stage that is moved or used by an actor)
(During the writing process further scenes characters and props can be added)
Then when the writing process begins I use a hot key to start writing what each character says
e.g. if I want to write this dialogue between Joe and Karen
JOE {insert TAB here} You really are very annoying!
KAREN {insert TAB here} What have I done this time? (She moves stage right and picks up a book)
JOE {insert TAB here} If you don't know, I am not going to tell you!
This would end up looking like the image below. The stuff in italics is a stage direction.
To write this I need hotkeys assigned to each character so that it writes the name and inserts a TAB.
I am not sure what keys to use, FN CTRL or ALT but in this example ALT K could be assigned to the KAREN character.
I need to occasionally change the look ( font, spacing tabs etc).
I need to print it out in booklet form.
I need to print it out in actor form. This prints in 14 point font with the name and dialogue of just one actor in BOLD. (To help actors memorise their role)
Each page should have Copyright Paul Hannah and the current year as a footer.
Finally I need to import my current plays so I can revise them.
• Review the existing code, pinpoint whatever changed in the Word 2013 object model or security settings, and remove the blockers.
• Restore every shortcut-key assignment and formatting behaviour so the macro once again automates those repetitive tasks seamlessly.
• Return a clean, commented macro that loads without Trust Center complaints and works on any fresh Word 2013 install.
If the fix requires minor refactoring or a module split, that’s fine—just keep the workflow identical from the user’s perspective. Once your updated macro passes a quick acceptance test (all key mappings fire, formatting looks right, and no errors appear), the job is complete.
This is the error that comes up.
Related categories:
Visual Basic
AutoHotkey
Debugging
Visual Basic for Apps
Scripting
Automation
Microsoft Word