Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 988
  • Last Modified:

PB and Sybase11 Connectivity Problem

Hi
I am working with PowerBuilder 5.0 on WIN 95.I have got two Backened databases on SYBASE 10 on SUN OS and Sybase 11 on HP.From my PB front end.Database of SYBASE 10 gets connected using the sybase conncetivity tool choosing the platform has win in the sybase connectivity platfrom and rest is fine.But when I try to get connected to SYBASE 11 it gives me the error below as
"ct_connect():protocol specific layer.interneal Client Library error:There is a tds state machine error.An illegal tds token sequence was received."
0
ajith_29
Asked:
ajith_29
  • 3
  • 3
  • 2
1 Solution
 
schneidCommented:
ajith_29,

Modify the locales.dat file in the locales subdirectory where the Sybase client is installed.  Find you platform and change the character set indicator (all entries for section) from CP850 to ISO_1.
0
 
ajith_29Author Commented:
i have sybase 10 on "iso_1" as default charc set and sybase 11 on roman8.
0
 
schneidCommented:
Can you providde the contents of sql.ini?
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
ajith_29Author Commented:
Hi schneid,
The coss,coss1 are working on Syabse 11 on roman8
The sunny,sunny1 are working on Syase 10 on iso_1
given below is the sql.ini file
[coss]
query=NLWNSCK,190.9.200.200,2222
[coss1]
win3_query=WNLWNSCK,190.9.200.200,2222
[sunny]
query=NLWNSCK,190.9.200.226,2000
[sunny1]
win3_query=WNLWNSCK,190.9.200.226,2000

0
 
david_levineCommented:
The way to get around this is in PowerBuilder, on the sqlca.dbparm= line, explicity specify the character set.

So, in your case, it would be the following for one application:
sqlca.DBAPRM='charset="roman8"'

and the following for the other application:
sqlca.DBAPRM='charset="iso_1"'

Of course, if you already had information previously specified for your PB DBPARM, you would just add the charset= parameter to it.

BTW, the suggestion for modifying the locales.dat file is fine, but only works if all the servers are using the same charset, which in your case is not true.

Let me know if that helps!
David





0
 
ajith_29Author Commented:
Hi david levine
Thanks for the perfect answer for my question.There is a small mistake not double couts a single counts work.So get the 100 points from me.
Bye
Ajith

0
 
david_levineCommented:
Ajith,

Ok, so award the points :)

Glad I could help and you have found the answer.

David
0
 
david_levineCommented:
Ajith... I think you responded on a different question.

You asked about what version of PB we are...

We are currently 32-bit and have been since PB 4. We are about to release a PB 6.5 version of our application.

David
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now