cancel
Showing results for 
Search instead for 
Did you mean: 

datawindow character length using ASA 16

t1950
Explorer
0 Kudos

PB 12.5.1 Build 4015, Win7 professional

When I create a dw using an ASA 12 db (or lower version), the character column lengths in the datawindow match the character length in the database. 

If I create the exact same datawindow using an ASA 16 database, the character columns in the datawindow are 3 times the size of the character lengths in the database.

Suggestions.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Tom;

  FWIW: I Just used PB 12.5.1 and 12.6 with SA16 (no longer called ASA BTW) and in every case - the DWO's all were built with the same character lengths as their SA tables VarChar & Char lengths. I can not reproduce your issue in my testing.

Regards ... Chris

t1950
Explorer
0 Kudos

Are you using build 4501?  pbdwe125.dll, pbodb125.ini and pbodb125.dll are all dated 1/20/2012.

Former Member
0 Kudos

Hi Tom;

  Yes, I was using build 4501 and all the DLL dates were 2012-01-20 14:35 (approximately).

BTW: It tried this on my W7 Professional development PC.

Regards ... Chris

t1950
Explorer
0 Kudos

I'm also using Win7 Pro (64 bit).

My SA 16 is 16.0.0.1761.

If it's not the PB dll's or the INI, can you think of another place to look?

Former Member
0 Kudos

FYI ....

t1950
Explorer
0 Kudos

Thanks for your replies.  see below.

Former Member
0 Kudos

Hi Tom;

FWIW: Here is the SA16 section from my "pbodb125.ini" ....

(C:\Users\<UserName>\AppData\Local\Sybase\PowerBuilder 12.5)

[SQL Anywhere]

PBSyntax='WATCOM50_SYNTAX'

PBDateTime='STANDARD_DATETIME'

PBFunctions='ASA_FUNCTIONS'

PBDefaultValues='autoincrement,current date,current publisher,current time,current timestamp,current user,last user,sqlcode,sqlstate,timestamp,null,user'

PBDefaultCreate='YES'

PBDefaultAlter='YES'

PBDefaultExpressions='YES'

DelimitIdentifier='YES'

PBDateTimeInvalidInSearch='NO'

PBTimeInvalidInSearch='YES'

PBQualifierIsOwner='NO'

PBSpecialDataTypes='WATCOM_SPECIALDATATYPES'

IdentifierQuoteChar='"'

PBSystemOwner='sys,dbo,sa_debug,rs_systabgroup'

PBUseProcOwner='YES'

SQLSrvrTSName='YES'

SQLSrvrTSQuote='YES'

SQLSrvrTSDelimit='YES'

ForeignKeyDeleteRule='Disallow if Dependent Rows Exist (RESTRICT),Delete any Dependent Rows (CASCADE),Set Dependent Columns to NULL (SET NULL)'

TableListType='GLOBAL TEMPORARY'

    Here is the DataWindow Painter section from my "pb.ini" ....  (C:\Users\<UserName>\AppData\Local\Sybase\PowerBuilder 12.5)

[Data Window]

GridOn=0

GridShow=0

GridX=8

GridY=8

new_default_datasource=5

new_default_presentation=2

Outline_Objects=1

PreviewOnNew=no

PreviewRetrieve=0

Preview_RetainData=1

PrintOnNew=Yes

PrintPreviewRulers=No

PrintPreviewZoom=100

Ruler=1

Status=0

stored_procedure_build=1

OverlayLineWidth=1

GenerateWSAssembliesOnCompile=YES

debug_ws_metadata=1

Regards ... Chris

Former Member
0 Kudos

Q: Are you using a LOCAL or Networked version of SA16?

BTW: My test SA16 DB is using the "Windows-1252" character set.

PS: Just created a UTF-8 DB and then recreated a table like in the Demo PB DB. No issues building a DWO from an SA16 DB encoded in UTF-8 ...

t1950
Explorer
0 Kudos

Problem Solved. 

My SA 11 database was created with CharSet windows-1252, My ODBC connection used a UTF-8 charset (it was so long ago i don't remember why, but i THINK it had to do with XML).  These settings did not cause the "too" long problem.

My SA 16 db was created with CharSet windows-1252, and my ODBC connection originally used UTF-8.  As soon as I removed the UTF-8 or set CharSet to windows-1252, the problem went away.

Thanks for all of your help.

Former Member
0 Kudos

Excellent news Tom!  

Now .... "Have you hugged your DataWindow today!"  

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi.

Are you using the same encoding in 16 and 12?

Andreas.

t1950
Explorer
0 Kudos

Both ASA 16 and ASA 12 are using UTF-8 for the charset