Thanks - we already rename it as SDAwPDF2.dll to save conflicts with any other installed copy. I had assumed that somewhere in the API there was a way to do confirm the location but if not I guess the best answer is to follow the same search process as Windows until the file is found viz (courtesy of MSDN):
1. The directory where the executable module for the current process is located.
2. The current directory.
3. The Windows system directory. The GetSystemDirectory function retrieves the path of this directory.
4. The Windows directory. The GetWindowsDirectory function retrieves the path of this directory.
5. The directories listed in the PATH environment variable.
Tony Bryer SDA UK