Access 2013 vba programming pdf

35a7 7 0 1 1 1. 9 2 2 2h16a2 access 2013 vba programming pdf 0 0 0 2-2v-4. 44A2 2 0 0 0 15. 68A1 1 0 0 1 5.

12a1 1 0 0 1 . M9 1a8 8 0 1 0 0 16A8 8 0 0 0 9 1zm. 69a4 4 0 0 0-. 29 0 0 1 1.

34 0 0 0 . 8 0 0 0 2. 07A8 8 0 0 0 8. 8 0 0 1 0-3.

83a8 8 0 0 0 0 7. 3A8 8 0 0 0 1. 77 0 0 1 4. I’m trying to figure out where to go here. I have simple condensed down my filepath, for obvious reasons – Note: It’s not a URL, but a file path if this matters.

Is this possible to do this way? I will continue to read other users posts in hopes to find a solution, and I’ll note here if I do find one. I’ve found a way to do this, just I have 1 small complication now. My database will be accessed by many users, possibly with different versions of Acrobat, or different locations. Now, here is my concern.

Does anyone have a suggestion as how to possibly get around this? Use comments to ask for more information or suggest improvements. Avoid answering questions in comments. Returns Null if no valid path is found. If all parameters are Null, Null is returned.

Wow, Thats awesome mwolfe02 – But wouldn’t that require me to know all the paths they may possibly have there Adobe Reader installed too? If so, this isn’t really a good method for me – as my office has probably on average 300 or 400 employees, and knowing each path they have it installed too would probably impossible. Thats a very cool function though, non the less! As I alluded to in my answer, it would depend on how much control you have over the setups. If it’s a corporate setup, those 300-400 employees might have Acrobat reader installed in only 5 or 6 unique locations. The other approach is to find the location of the executable through the registry.

The problem with acrobat reader is you have to account for different versions. You could ask each user to browse to the path of their local copy of acrobat reader. This is more than many users are capable of, though. You’d need to be prepared for the tech support fallout. The problem with this approach is that the user might be using a different default pdf reader.

You would have to account for that somehow. In the long run, I find it far simpler to maintain if not quite as elegant. Registry keys are the better way to go, unlike file locations they have consistency between systems. Below are three functions, two in support of one, and a macro which tests the functions. This removes the hassle of typing out many different key locations for each version and provides some amount of coverage should future versions be released and installed on a user’s system. In fact, mwolfe02 and I both have our keys in the same location, though I am using version 11 and he, at the time of writing, was using 10.