, packaged when prompt original concept Runtime Packager can only work with the original concept 9.0 Enterprise edtion with all components installed. Both Please reinstall original concept of 9.0, and try again. If there are any other third party packaging, what is the software

CodePudding user response:

Packaging machine can only use pb 9.0 pb runtime enterprise with all components installed,
Please reinstall 9.0 pb, try again

CodePudding user response:

1. Put all the DataWindow object stored in a DW. PBL file;
2. All other objects stored in another APP. PBL file;
3. The increase in application of the Library list DW. PBL entry;
4. Generate a Project (Project), at a specified generation APP. EXE files at the same time, generate DW. PBD file (under the Library list of DW. PBL DLL in central columns selected)
5. Put the following files can be stored in the same directory from 9 normal running:
APP. EXE DW. PBD PBDWE60. DLL PBSYC60. DLL PBVM60. DLL

CodePudding user response:

The simplest way is to use PB comes with the original concept of the Runtime Packager, start menu there,

CodePudding user response:

reference 3 floor response:

the simplest way is to use PB comes with the original concept of the Runtime Packager, start menu there,

Is his pb how to install all is not generated

CodePudding user response:

Pb is pseudo code, similar to Java, so it needs the support of a series of DLL, as long as the DLL put together with the PBD, generally no problem

If set to a DLL?
The most stupid method is: in a clean environment, has the operating system on the installation of pb, copy all of the DLL under the share directory in the past, and then selectively deleted some DLL, lack of DLL will be an error, and gradually to the minimum to determine the required DLL runs down
If you don't want to so complicated, use pb packaging tools, an environment play packages, and then carry out the environmental package to a new directory, the new DLL in the directory are copied to the program directory.

CodePudding user response:

reference 3 floor response:

the simplest way is to use PB comes with the original concept of the Runtime Packager, start menu there,

is the packaging problems with it

CodePudding user response:

Should is my caused by PB no full, well armoured

CodePudding user response:

refer to fifth floor response:

pb is pseudo code, similar to Java, so it needs the support of a series of DLL, as long as the DLL put together with the PBD, generally no problem

If set to a DLL?
The most stupid method is: in a clean environment, has the operating system on the installation of pb, copy all of the DLL under the share directory in the past, and then selectively deleted some DLL, lack of DLL will be an error, and gradually to the minimum to determine the required DLL runs down
If you don't want to so complicated, use pb packaging tools, make a ring...

this is also too difficult...