I write call DLL, ocx controls in the DLL will invoke other DLLS, now when installing the 32-bit system put ocx and all of the DLL in system32 through HTML calls, in most of the Windows 7 system call normally, but in a small number of system prompt R6034 error
I use TSTCON32. Exe test call ocx, only TSTCON32 ocx, DLL in the same directory, know what the problem is not to have excuse me

CodePudding user response:

See many R6034 as a DLL not online registration, the relationship between register under give it a try

CodePudding user response:

In a 64 - bit Windows:
64 exe and DLL in the directory c: \ Windows \ sys tem32 directory.
32 bit exe and DLL in the directory c: \ Windows \ sys wow64 directory.
So pay attention to:
In win64 system registered under 32-bit ocx DLL to 32 ocx or copy the DLL to the c: \ Windows \ syswow64 \ directory,
And registered to c: \ Windows \ syswow64 \ regsvr32 XXXXXXX ocx or DLL
Under win64 a system set up 32-bit programs use a database alias to c: \ Windows \ \ syswow64 \ cliconfg exe
Under win64 a system set up a 32-bit application system DSN to c: \ Windows \ \ syswow64 \ odbcad32 exe
A 64 - bit Windows platform attention point of the file system redirection http://www.cnblogs.com/jiake/p/4981555.html
64 - bit Windows platforms attention point of the registry to redirect http://www.cnblogs.com/jiake/p/4956218.html

CodePudding user response:

You can directly use the DLL with your ocx component DLL in a directory, install together, so call can't find the time will not happen