start numbering from a particular page in word 2011 for mac

#Start numbering from a particular page in word 2011 for mac 64 Bit
#Start numbering from a particular page in word 2011 for mac full
#Start numbering from a particular page in word 2011 for mac mac
#Start numbering from a particular page in word 2011 for mac windows

Private Declare PtrSafe Function fread Lib '/usr/lib/libc.dylib' (ByVal outStr As String, ByVal size As LongPtr, ByVal items As LongPtr, ByVal stream As LongPtr) As Long Private Declare PtrSafe Function pclose Lib '/usr/lib/libc.dylib' (ByVal file As LongPtr) As Long Private Declare PtrSafe Function popen Lib '/usr/lib/libc.dylib' (ByVal command As String, ByVal mode As String) As LongPtr

#Start numbering from a particular page in word 2011 for mac full

Note that due to a change in sandboxing, the full path to the libc must be used in the declarations otherwise you'll end up with an error 53 'File not found' on never versions of OSX/Office.

#Start numbering from a particular page in word 2011 for mac 64 Bit

That is indeed one, two, and then three double-quote characters! (presumably escaping the double quotes)įor anyone using 64-bit Office here's Robert's code updated to be compatible with both 32 and 64 bit versions. I was able to just double my double quotes and put it in double quotes after the MacScript code: MacScript 'do shell script ''parseCsvAndOpen.sh''' Now copy your simple script from AppleScript Editor to your vba and confirm it still works

The good news here is that you have a narrower search if you need to go back to StackOverflow or Google for help -).

Track down any issues, make changes, and repeat hitting the 'Run' button until you get it to execute from within AppleScript Editor.

Type your simple script into the new file without doubling the double quotes - mine reads do shell script 'parseCsvAndOpen.sh'

In Spotlight, start typing 'applescript editor' until it shows up and then click on it.

Use AppleScript Editor to confirm that the script actually works as whatever user and with whatever environment variable happens to be used: Here is my recommendation, which hopefully gives better insight during your troubleshooting than the meaningless Excel errors I was seeing before I used AppleScript Editor: To get my script to work, I had to resolve some path and permissions issues (not the script itself, but things touched by the script).

#Start numbering from a particular page in word 2011 for mac mac

Note that several of the Long arguments in the above example are pointers, so will have to be changed if a 64bit version of Mac Word is ever released.Īnother problem presents exactly like this: permissions cause your script to fail due to differences between the AppleScript environment and your user's bash environment.

Result = execShell('echo Hello World', exitCode)ĭebug.Print 'Exit Code: ' & str(exitCode) Read = fread(chunk, 1, Len(chunk) - 1, file) Private Declare Function feof Lib 'libc.dylib' (ByVal file As Long) As Longįunction execShell(command As String, Optional ByRef exitCode As Long) As String Private Declare Function fread Lib 'libc.dylib' (ByVal outStr As String, ByVal size As Long, ByVal items As Long, ByVal stream As Long) As Long Private Declare Function pclose Lib 'libc.dylib' (ByVal file As Long) As Long Private Declare Function popen Lib 'libc.dylib' (ByVal command As String, ByVal mode As String) As Long If you want to get the output from the command, you could use popen(). The downside is that it has quite a lot of overhead (100-200ms per call).Īnother alternative is the system() function from the standard C library: Private Declare Function system Lib 'libc.dylib' (ByVal command As String) As Long This is likely to be the simplest option and what I would suggest doing. The MacScript() VBA function can also be used: MacScript('do shell script ''command''').

#Start numbering from a particular page in word 2011 for mac windows

It also doesn't appear to accept arguments as it does on Windows (reporting a 'Path not found' error if any arguments are added). The Shell() VBA function on Mac appears to require the full path as an HFS-style path (with colons instead of slashes).