on 10-31-2015 7:53 PM
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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.
Hi.
Are you using the same encoding in 16 and 12?
Andreas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.