Win 7 64 - bit systems, pb9 call external DLLS, didn't find the target directory DLL files, must copy the file to the Windows \ SysWOW64, or is the DLL files in the directory, and then to add this directory to the path the path, so there is a problem, if the development environment call external DLL, the DLL file is copied to the system directory will cause more confusion, if different program calls the DLL file with the same name, but different version, will not be able to solve (need to make a copy of the current development program DLL used to cover the same file, considerable trouble), and, if we can through the way of setting parameters or modify the registry, change the win 7 64 - bit under pb9 runtime DLL search path or the process of the order,,,

CodePudding user response:

I PB9 application Windows 7 a lot of customers, whether your shortcut didn't work path set?
Generally suggested that the DLL on your application EXE directory at the same level, call when you try to get a current path
In addition, there is a way, you can set this application to winxp compatible way to run

CodePudding user response:

I'm not saying the compiled program, I mean the environment of development, the development environment is running, can't find the current directory DLL, the DLL must be copied to the Windows \ SysWOW64 directory, or on a specified directory, and then add the directory to the path, such easy to cause the development environment is chaotic situation, because the copy the DLL under the Windows \ SysWOW64 too much, bad also handle version is different, the same name as the problem, don't know what happened with 64 - bit Windows DLL search path change???????

CodePudding user response:

No one answer, your top, this problem may be to MSDN only to find the answer, but I know about the MSDN is too little,,,

CodePudding user response:

Windows 7 64 - bit does have such a problem, especially when the old dynamic library, I try to call vs2010 32-bit c + + dynamic libraries also have same problem

CodePudding user response:

Happens is a change in the call search path, or why, what's the good solution?

CodePudding user response:

Still did not find the right solution

CodePudding user response:

With method, pb11.5 also this problem under the Windows 7 64, compile operation no problem, in the development environment, it can't find the DLL, can only be copied to the system32 or add path path, all quick tortured mad

CodePudding user response:

Sorry to ask what your problem is not related question,
I pb9 installed on Windows 7 64, with your oracle 10 g 64, installed the oracle client
But the pb is oracle can not connect to normal, do you have encountered this problem, can dispel doubts about?

CodePudding user response:

Pb9 no patch? A 8836 patches.

CodePudding user response:

Pb9.0.2 7534 version said no pressure, under win64 development N for a long time, has been normal
This machine also installed version are
Pb11.2 8669
Pb11.5 3127
All three versions in normal

CodePudding user response:

The question has bothered me for 3 days, hasn't been solved, put the DLL \ Windows \ SysWOW64 also tried inside, or not, but an accidental idea can let I tested the incredibly, is inside powerbuilder9 attribute the compatibility mode change, to winxp. Test no problem. Happy...

CodePudding user response:

reference 13 floor chaijun0221 reply:

this problem bothering me for 3 days, hasn't been solved, put the DLL \ Windows \ SysWOW64 also tried inside, or not, but an accidental idea can let I tested the incredibly, is inside powerbuilder9 attribute compatibility mode change, to winxp. Test no problem. Happy...

Thank you very much!!!!!! It's possible! Thank you again!