Word macro erroring out

Hello! I have a macro that we run with Word. I have one user however who is having debug errors popping up when running the macro on files that have been successfully run by other users using the same versions of Word. Can someone take a look at it and tell me if there is anything I can try to get it working for her again? Again, it is just one user, the rest of us have no problems and get no debug errors doing the same thing.
tab2doc.txt
mrosierAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

GrahamSkanRetiredCommented:
What is the error message, and on which line does it fail?
0
mrosierAuthor Commented:
Well it stops with : "Code execution has been interrupted" and line 34 is highlighted: ".TopMargin = InchesToPoints(1.25)". From there, if I continue, all the lines under it will stop the macro as well, but it begins there. Again, there are no problems with anyone else. Is there a way to completely reset Office or just Word to default and try again?
0
GrahamSkanRetiredCommented:
That message should only happen if the user hits Ctrl+Break.

There might be some anomaly in Word's cached settings for that user profile. Try a creating a new one on that system or try the fix(es) here:
http://support.microsoft.com/default.aspx/kb/921541
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

mrosierAuthor Commented:
I tried using another user profile entirely on that computer and I still get the debug error. To avoid crawling through the registry and that list, would an uninstall and reinstall be just as good? I would prefer to do that if so, because I can do other things while it runs.
0
GrahamSkanRetiredCommented:
Generally un-install and re-install does not fix this type of problem. By design,  Microsoft tries to maintain user settings in those circumstances.

Ulness it is very inconvenient, do at least try the new user profile. This is a quick test. If it succeeds, then you can move on and apply the fix in the Microsoft link to the old profile.
0
mrosierAuthor Commented:
should I try recreating the same profile though? I signed on with a different profile entirely and it still happened.
0
GrahamSkanRetiredCommented:
No. If another profile produces the same result, then it is unlikely to be a profile problem.
Since it seems to be a reaction to a particular keystroke combination that hasn't been reported by the user,  perhaps you should try replacing the keyboard.
0
mrosierAuthor Commented:
well the keyboard is not in use at all. We just use the mouse to run the macro by going into the Word file<View<Macros<View Macros. Then we select the macro in question and hit Run. No keystrokes involved.
0
Chris BottomleySoftware Quality Lead EngineerCommented:
Sorry to butt in because when it comes to Word VBA I look to Graham for the best in class.

Is the printer and paper selection the same for all the pc's... i.e. is it within the capability of the selected printer to do this bit of code?

Chris
0
GrahamSkanRetiredCommented:
Yes, but the macro acts as if Ctrl+Break was hit while the macro is is in progress.
0
Chris BottomleySoftware Quality Lead EngineerCommented:
No argument from me ... just wondering that since printer selections cannot be detected during code development and can only occur at run-time it seems to me possible that for example there is an issue with the document size etc such that at run time it trips.

NOte I appreciate there might be a range of possible error codes for the scenario but since i'm not clever enough to know them all I am simply suggesting a check of printer/paper definition *may* elicit some useful information.

Chris
0
mrosierAuthor Commented:
Ok folks, eventually the computer was rebooted for whatever reasons on the user's part and that stopped the errors. It now works as it should again. Does this make any sense as a solution?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DrTribosCommented:
Only if you are using windows...
0
mrosierAuthor Commented:
Yes this is a Windows XP Pro machine
0
Chris BottomleySoftware Quality Lead EngineerCommented:
The perils of humour I fear:

"the computer was rebooted ... Does this make any sense as a solution?"
begat:
"Only if you are using windows..."

If i'm not very much mistaken.

Chris
0
mrosierAuthor Commented:
yeah I was thinking that too, but I am way way too reliant on tone of voice and completely  miss it sometimes with just text :p. Does anyone know how I should close this question then? I am not sure where to go from here.
0
Chris BottomleySoftware Quality Lead EngineerCommented:
I cannot speak for Grahams involvement but it seems to me that that despite any input from us the resolution was a reboot and whilst some of the thoughts might have had a bearing we cannot be sure.

From my perspective I wouldn't disagree with deletion of the question.

Chris
0
mrosierAuthor Commented:
well unless anyone objects, I will delete the question. Graham, do you object to that?
0
GrahamSkanRetiredCommented:
Don't delete it. Close it with the reboot comment (39460539) as a solution. If it happens to someone else, it could be useful.

It's a reminder to all of us that restarting the system should be tried for all weird problems.
1
DrTribosCommented:
I agree with Graham, and I also think it is a valid solution for a windoze sys ;-)
0
mrosierAuthor Commented:
Ok folks, will do, thanks!
0
mrosierAuthor Commented:
The system had to be rebooted eventually which is not a fix with an explanation really, so the cause will not be known
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Word

From novice to tech pro — start learning today.