Hi Tom -
I don't have all the answers, but at least I can let you know what those
who
*can* answer will need to know:-)
First, if the users are running Word 2008 your first assumption is correct
-
Office 2008 does NOT sup****t any version of VBA, so the macros won't run.
My
gut reaction is that this is the case here. If so, AppleScript to replace
the code may be an option. OTOH...
If they're using Word 2004 or prior your code will have to be tweaked but
it
should run. Mac Office is approximately 1 version behind in VBA, so if the
code was written in a more recent version than what's used on Macs the
differences may cause it to not run at all. That's the part I can't answer
for you, but there are other regulars in the group who can.
They'll need to know Mac Word/Office versions, VBA versions and probably a
copy of the code itself.
Regards |:>)
Bob Jones
[MVP] Office:Mac
On 5/6/08 12:54 PM, in article OHQvWn5rIHA.672@[EMAIL PROTECTED]
"Tony"
<|toxendine@[EMAIL PROTECTED]
|> wrote:
> Hi All,
>
> I'll start by saying that I have no experience with Macs, so please be
> patient with me...
>
> I've got a Word template that we've pushed out to some of our vendors
that
> runs a few macros when a new do***ent based on the template is created.
Up
> until this point we've only had to roll it out to vendors using PCs but
now
> we have a vendor in a Mac environment who can't use the template. The
> vendor creates a new do***ent from the template, is prompted to allow or
> disallow macros (he allows them in this instance), and the do***ent is
> created but the macros do not run. So, I'm assuming that:
>
> 1) The vba code will not work at all
> 2) I need to tweak the code to work with Word for Mac
>
> In either case, I'm not sure where to start and hope someone can point
me in
> the correct direction. Thanks in advance for any help you can offer.
>
> Tony
>
>
|
