I did a FULL BUILD before doing the DEPLOY.

The end result is a 32K executable, when the size should be closer to 16K.

Hi Olan, with "Deploy" I mean, right mouse click on the target and choosing "Deploy". Beware that if you have more than one project, it might use any project you don't want. In that case you'll just have to open up the project and click on the icon to deploy.

Why is it bad that the executable is bigger when you don't generate PBDs? You said it yourself: " if you UN-check the PBLs on the Libraries tabpage of the Project file, all the code compiles into a single EXE."

This logically means that the exe will be bigger if you don't generate pbd files.

Maybe I'm not understanding what's going on.

regards

Hmm I think you have a typo when you say 32K vs. 16K? Did you mean 16,000 K?

If the executable doesn't work, but does compile without warnings, most likely you are missing some dynamically assigned datastores or datawindows and/or dynamically created / opened user object usertabs. search on "Create using some_string_variable" and OpenTab() and openuserobject() and opentabwithparm and openuserobjectwithparm.

Ha, I get it Sivaprakash. VB 6 didn't need the .net framework.

Olan,

To run the exe created with Powerbuilder, without Powerbuilder runtime files (as we get exe in VB 6 that could be run without any VB runtime(s). )

VB6 has a runtime DLL.

If that's the case he should be able to put them in the PBR file.

Kevin,

Yes there is a PBR file, hope Olan would have included the required dw names' in it.

Apologies.

An EXE is generated, but the size of the executable file is 32KB when it should be 5 to 10 times that size.

In PBv12.1, nearly the same code creates an EXE of 15,483KB.

I try the 32KB exe anyway, tand the utility fails to even open.