Kbase P142053: Report Builder Engine: How is the search for the PROEXEC.DLL Dynamic Link Library conducted?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/26/2009 |
|
Status: Unverified
GOAL:
Report Builder Engine: How is the search for the PROEXEC.DLL Dynamic Link Library conducted?
GOAL:
Does the search for the PROEXEC.DLL follow the PROPATH?
FACT(s) (Environment):
Windows
Progress 9.x
OpenEdge 10.x
FIX:
The PROEXEC.DLL is called as an external procedure from the following Report Builder Engine related procedures: _rbuild.p, _prntint.p and _prore.p.
When PROEXEC.DLL or any external procedure is executed, the system is asked to load the DLL.
The 4GL/ABL PROPATH has no effect in this context and the search order strictly follows Windows search order rules for a DLL which are generally along the following lines. Check the Microsoft documentation for further details.
1. The directory from which the application loaded.
2. The system directory returned by the GetSystemDirectory function.
3. The 16-bit system directory.
4. The Windows directory as returned by the GetWindowsDirectory function
5. The current directory.
6. The directories that are listed in the PATH environment variable.