[AccessD] External dependencies

[Ryan W]

I have some code that does some PDF assembly and manipulation via a
commercial product that up until the most recent version has COM binding so
I could do it all natively in Access.

The latest version dropped the COM library but has some features I
want/need.

I re-wrote the code in python using their trial libary and used a utility
to bundle that as an exe so I don't have to concern myself with making sure
all the users have python installed but instead can just launch the
executable (from code) with a couple command line switches to pass in data
needed for output.

I'm really not a fan of having external dependencies if I can avoid them.
More stuff to bundle/remember/set up when deploying new workstations and
such.... but I guess "it is what it is".

Anyone have any pointers, gotchas or words of wisdom for scenarios like
this?