I am having troubles with setting the reference to Adobe Acrobat from Excel VBA which is running on a Mac.
Let me provide a bit of background:
I have been programming VBA within Windows in Visual Studio, Access and Excel for a couple of decades. So I am very comfortable with both Windows and VBA. Recently, thanks to some assistance from one of the forum questions I posted, I was able to beginning writing an Excel program which interacted with the various forms I created with Adobe Acrobat Pro DC for my windows laptop to retrieve information from the form to various tabs within the Excel workbook, my first venture with Excel/Adobe interaction.
I was doing all of this for a friend. Unfortunately, my friend has a Mac. So now I am trying to get this Excel workbook to work on his Mac with the loaded Office. However, I have run into a big problem with regards to the reference to Adobe Acrobat.
He also has installed Adobe Acrobat Pro DC on his Mac (he has even tried to make minor changes to a few forms). Since he is not technical savy, he has no idea what I am talking about with regards to trying to solve the "Adobe Acrobat 10.0 Type Library" reference error. And since I don't know my way around a Mac, I don't know where to look or what to look for.
So it boils down to the following:
-I have an Excel macro that works successfully on Windows that references Adobe Acrobat Pro DC (reference solved without my assistance)
-I have moved that same Excel macro workbook to a Mac
-Adobe Acrobat Pro DC is installed on both the Windows laptop as well as the Mac
-The "Adobe Acrobat 10.0 Type Library" reference on the Mac is unresolved and I have no idea how to resolve it as I am not a Mac user.
So in some ways, this is a Mac vs PC question but it is trying to solve the Adobe reference. So I hope someone here might be able to provide some guidance or suggestions.
Thanks in advance,
You are using a capability/API not provided on Mac.
I should add, the Acrobat IAC documentation gives the Mac implementation, based on AppleScript. Entirely different API, not a drop in replacement.
Is there an official response to solve this problem from Adobe team ?
The response is still true and complete. What makes you think you need an official reply? Do you find something in the documentation suggesting I am wrong?