Made of PB + SQL system, packaged installer requires the DLL files, can be used in other installed on the machine. I use the packaging process is: the Setup Factory V7.01 localization version (fourth edition)

CodePudding user response:

Dbmsadsn. DLL dbmsgnet. DLLDBMSRPCN. DLLDBMSSHRN. Dlldbmssocn. DLLDBMSSPXN. Dlldbmsvinn. Dlldbnetlib. DLLDBNMPNTW. Dlllibjcc. DLL

Libjsybheap. DLL, ntwdblib. DLL, pbdwe90. DLL, pbmss90. DLL, pbsys90. DLL, pbtra90. DLL, pbvm90. DLL


Seems more and more a few no harm

CodePudding user response:

And want to see your program inside what calls the DLL

CodePudding user response:

The most basic:
SQL: direct way
Dbmssocn. DLL
Ntwdblib. DLL
Pbmss90. DLL

Pb:
Pbvm90. DLL
Pbdwe90. DLL
Libjcc. DLL

Other see the specific procedures of ~

CodePudding user response:

The original concept Runtime Packager
The packaging tool to pb9 bring their own. All PB Dll and the database interface Dll

CodePudding user response:

reference 4 floor jlwei888 response:

original concept Runtime Packager
The packaging tool to pb9 bring their own. All PB Dll and the database interface Dll

I don't know yet, learning the==!

CodePudding user response:

reference 4 floor jlwei888 response:

original concept Runtime Packager
The packaging tool to pb9 bring their own. All PB Dll and the database interface Dll

Positive solution

CodePudding user response:

reference SOFTFUN_CSDN reply: 3/f

basic:
SQL: direct way
Dbmssocn. DLL
Ntwdblib. DLL


Pb:
Pbvm90. DLL
Pbdwe90. DLL
Libjcc. DLL
Pbmss90. DLL

Other see the specific procedures set ~

CodePudding user response:

To learn