I would expect columns to be "identical width - or almost identical". In your example I see

• Everything have comparable Height and Y whereas Width and X differs
• Columns ID=1, 2, and 3 increased width by 20%
• Label for ID=3 increased width by 22%
• Column ID=4 is just 9% wider

So I would look for following "potential differences" as root cause. You may find more than one apply to your scenario:

• Are X and Width the ONLY differences in generated code PB-old vs. PB-new?
  The additional differences may indicate what the reason is.
  
  
• Does DataWindow syntax become "identical" when you convert the DataWindow's units from PBU to pixels?
  Different screen config impacts pixel-to-PBU ratios.
  
  
• Are database column definitions identical when PB-old and PB-new created the DW syntax?
  Column definition may change over time or differ in DEV vs. TEST vs. QA vs. PROD environments
  Example > number(15, 2) => number(17, 4)
  
  
• What is max DECIMAL size in your PB-old vs. PB-new?
  PowerBuilder changed limit on DECIMAL type at some point; I don't remember which version.
  That potentially requires more space to fit large values.

HTH /Michael

Greetings, Julian - 

Is the same Windows printer selected in each version. PB uses the properties of the currently selected printer when generating syntax.

Do you have access to a pre-2017 version of PB later than version 9 (v12.5 or 12.6, for example) that you could try this with? I'm curious what the results would be.

Regards, John

I still have PB9 up if you want me to test it.  I can't see from your picture but did you set the font. PB9 defaulted to MS Sans Serif, PB2019 defaults to Tahoma and they are different sizes.

1234567890ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz Tahmoa 8

1234567890ABCDEFGHIJKLMNOPQUSTUVWXYZabcedfghijklmnopqrstuvwzyz  Arial 8

The example uses Ariel as this window does not have MS Sans Serif as an option

Hi all,

Update: this is an example of the code used to build our dynamic dw.

// SQLCA.DBMS = "OLE DB"

ls_select = "Select EmpresCod, SucursCod, ClientVtasCod, ClientVtasNomb From ClientesVentas"

ls_estilo = 'Style ( Type = Tabular Horizontal_Spread = 20 Vertical_Spread = 25 ) ' + &
'Datawindow ( Color = ' + String ( RGB ( 255 , 255 , 255 ) ) + ' ) ' + &
' Column ( Font.Face = "Ms Sans Serif" Font.Height = -8 Font.Weight = 400 ' + &
' Border = 0 Color = ' + String ( RGB ( 0 , 0 , 0 ) ) + &
' Background.Mode = 1 Background.Color = ' + String ( RGB ( 255 , 255 , 255 ) ) + ' ) ' + 'Text ( Font.Face= "Ms Sans Serif" Font.Height = -8 Border = 6 Color = ' + String ( RGB ( 0 , 0 , 0 ) ) + ' Background.Mode = 0 Background.Color = ' + String ( RGB ( 255 , 255 , 255 ) ) + ' ) '

ls_sintaxis = SQLCA.SyntaxFromSQL ( ls_select , ls_estilo, ls_errores )

Update 2: attached there is an image comparing the results of running this snippet in 3 different versions of PowerBuilder. You can see there that PB 9 = PB 11.5 and the difference occurs in PB2017.

Greetings !!!

_______________

Julián Tagarro

NeoSistemas SRL

Hi Julián;
 
   FWIW:  You can always "standardize" any Table & Column's look an feel by entering the font, default dimensions, colour, edit style, etc properties in the DB Painter for each Table & Column. These are called "extended attributes" and are stored in the PBCATxxx tables in your DEV DB Server. If you export these PBCATxxx tables and their data from your DEV DB server over to the Prod DB server, the SyntaxFromSQL() command will utilize these "extended attributes" look & feel standards on every dynamic DWO also in production.Thus over-riding the PBVM "on-the-fly" calculations for default font, size, colour, etc. Making the PROD environment now identical to your DEV environment when using the SyntaxFromSQL() command for any Table/Column referenced.

Food for thought.  ;-)

Regards ... Chris