I am using 3rtParty dll's in my progress application.
Redistribute then in a subdirectory named bin in my application.
A specific module of this 3rtParty can not been used while the dll is not the the application DLC.
And not specifies in the PATH system environment variable.
Would like to check the system path if the 3rtParty bin is included and add it when it is not there during my application startup procedure.
Can someone advice me?
The basic dll's I load PERSISTENT to interact with this 3rd Party Tool (maned List&Label from Combit).
For some mail option it calls other DLL from those I have loaded. The location of them are in the same folder which I have included in my propath as well but based on debugging log files they explained the following:
Analysing the log file we can see that the application and the modules are stored in two different directories:
Application : C:\PSC\OPENEDGE116\BIN\PROWIN.EXE [188.8.131.527]
List & Label : C:\ABS\ABS422\STAND\BIN\CXLL22.DLL [22.1.2016.36315 (16-12-22 15:14)F]
If the directory containing the cxMX22.dll is not in the PATH system environment variable from Windows, then the application does not find the module.
So I have to add the folder to the PATH.
I would not go to all network computers to set PATH adjustment manually.
But just control it central from the application.
Thank you kindly for your guiding. Have to get myself familiar with this CreateProcess API.
You an example on this to start a progress 11.6.3 64bit application.
Which uses an ini files as startup parameter.
You may be able to use SetDllDirectoryA to add the directory to the DLL search path before loading the third-party DLL. The following KBase article has the external procedure definition for SetDllDirectoryA.
As shown in the article, you will need to reset the DLL search path after you're done with the third-party DLL by doing the following: