Mac Forum / Applications / Word / May 2008

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 support 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@TK2MSFTNGP02.phx.gbl, "Tony"
<|toxendine@hoopercorp.com|> wrote:

Hi Tony:

The fact that he is getting the Enable Macros prompt indicates that he has a
version of Mac Office that still contains the VBA Interpreter: so he is at
Word 2004 or earlier.

In Word 2008, VBA code will be silently ignored, because there is no VBA
runtime in Office 2008.

VBA in Office Mac has not advanced beyond VBA 5.  So you need to dust off a
copy of Word 2000 and compile there: anything that won't compile in Word
2000, will not compile on a Mac.

The general idea is to surround the stuff that won't compile with "Hash
Defines".  These are compiler directives that tell the Mac compiler to
compile a different set of statements to the PC compiler.

Syntax
#If expression Then
   statements
[#ElseIf expression-n Then
   [elseifstatements]]
[#Else
   [elsestatements]]
#End If

For example:

   #If Mac Then
     .Protect Password:="", NoReset:=False, Type:=wdNoProtection
   #Else
   .Protect Password:="", NoReset:=False, Type:=wdNoProtection, _
        UseIRM:=False, EnforceStyleLock:=True
   #End If

If I were you, I would put all of your hash-defines in a separate module,
because you will have to tweak them for each new version of Mac Office and
PC Office :-)

You also need to explain to your vendor that if they remove Office 2004,
your template will be instantly disabled, and there is nothing you can do
about that.

So they need to remain on Office 2004 for Mac, or install a PC :-)

For more information, send me an email at john@mcghie.name and we'll take
this offline.  Note:  HTML email or attachments are unlikely to survive the
spam filter :-)

Cheers

On 7/05/08 2:54 AM, in article OHQvWn5rIHA.672@TK2MSFTNGP02.phx.gbl, "Tony"
<|toxendine@hoopercorp.com|> wrote:

OK Guys, if I understand you correctly, verifying the version of Word the
user has is the first step.  2004 Or earlier & I can make something work by
tweaking the code appropriately and compiling in Word 2000.  2008 And all
bets are off.

Here's the code that's running; it's very simple but I have no idea how to
tweak it appropriately but will check out the Mac MVP site.  Any suggestions
are appreciated, of course...

There are a couple of fields, each of which I'd like to prepopulate when a
new doc is open, to generate 'unique' information to identify new docs as
they come back to us.

//CODE START//

Private Sub Document_New()
On Error GoTo Err_Document_New

   ActiveDocument.FormFields("txtTestDate").Result = Format(Now(),
"m/d/yy")
   ActiveDocument.Bookmarks("txtTestDate").Range.Fields(1).Locked = True

   ActiveDocument.FormFields("txtPoNumber").Result = "SKAR" & Format(Now(),
"HhNnSs")
   ActiveDocument.Bookmarks("txtPoNumber").Range.Fields(1).Locked = True

Exit_Document_New:
   Exit Sub

Err_Document_New:
   MsgBox Err.Description
   Resume Exit_Document_New

End Sub

//CODE END//

Thanks for the feedback and assistance.  I appreciate the help.

Ciao,

Tony