Heavily VBA coded Word template setup on PC - best way to get it to run smoothly on a Mac

Hi experts.

I have a heavily VBA coded Word 2010 template. It is setup on PC. It calls dialog boxes, inserts data from Excel, etc. etc.

One of my users now has a Mac, running Microsoft Office for Mac 2011, but they get error codes galore when accessing any of the macros.

Is there an easy solution to this problem? For instance if you installed something like Virtual PC for Mac, would that resolve the issue? And is so, how does that work, do you install Virtual PC for Mac and then you install the Windows version of office????

Love some advice!
Who is Participating?
byundtConnect With a Mentor Commented:
I use a Mac, but spend most of my day using Excel for Windows. I do this using Parallels virtual machine, which is much faster than Virtual PC ever was. I also use Word for Windows. Both Word and Excel are pretty snappy on my 2008 MacBook Pro, even running macros--and I'm a power user.

To follow this approach, you will need to install Parallels (or VMware), a licensed version of Windows and a licensed version of Office. The benefit of this (as opposed to using BootCamp, which is free from Apple, a licensed version of Windows, and a licensed version of Office), is that you can switch between Mac and Windows apps very easily.

Both Parallels and VMware update their Mac products every year (and have just done so).

Note that you may also want to budget for a Windows antivirus program if you take that approach.
Chris BottomleyCommented:
I used to use Parallels to run Windows in a virtual machine but with lots of low level macros accessing PC resources a significant number of them gave me issues.  It may be that this was a lack of knowledge on my part but I now run a PC as well where I can produce and maintain macros so my own experience is that if your template uses low level resources then it is at risk.  Relatively simple macros which do not use such resources may be convertible ... for example file paths can be assembled using Application.PathSeparator rather than the forward/backward slash explicit character.

Fi69Author Commented:
Thanks byundt. I took your advice and installed Parallels, Windows & Office and have tested the macros and it works perfectly! Thank you.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.