Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Sybase ODBC connect on Powerbuilder 2017 R2

  1. How-to
0
Votes
Undo
  1. bryan hui
    bryan hui
  2. PowerBuilder
  3. Monday, 30 July 2018 13:43 PM UTC

Dear users,

Does anyone use Sybase ODBC driver  to connect.

If yes, would you like to advise the "PB".ini entry setting.

We migrate from PB5 and use

Reference links： http://publib.boulder.ibm.com/tividd/td/TRM/GI11-0862-00/en_US/HTML/tdserm1133.htm

Required driver: ODBC Driver for ASE 1.4 https://www.devart.com/odbc/ase/download.html
 

to setup

C:\Windows\ODBC.ini

[ODBC 32 bit Data Sources]

TSZX SYC sybase CT lib=Devart ODBC Driver for ASE (32 bit)

and successfully connect thru. DB profile under Powerbuilder 2017 R2.

 

However, when we

After amend  d:/icil/lib/clib.ini

Amend DBMS=TSZX SYC sybase CT lib.

On user object to connect.

It says Cannot Connect [DBMS TSZX SYC sybase CT lib is not supported in your current installation].

 

Use of NOT EXISTS or EXCEPT in datawindow SQL
Issue with the new forum software
Responses (3)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Monday, 30 July 2018 14:22 PM UTC
  2. PowerBuilder
  3. # 1

If for some reason you must use ODBC, an ODBC driver comes with ASE OpenClient. I'm not sure how it compares performance wise with the one you are trying to use.

Comment
There are no comments made yet.
bryan hui
bryan hui Accepted Answer Pending Moderation
  1. Monday, 30 July 2018 14:06 PM UTC
  2. PowerBuilder
  3. # 2

Dear Chris,

Thanks for your quick and detail response..

We will check and have a try..

Thanks a lot.

regards

bryan

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 30 July 2018 14:01 PM UTC
  2. PowerBuilder
  3. # 3

Hi Bryan;

 

     First of all, PB supports ASE natively for way over a decade now. Just set your Transaction Object (or DB profile) to: SQLCA.DBMS = "ASE" and you should be talking natively to ASE and processing much faster than ODBC - which is a middleware connection to your DBMS. That is to say the SQL coming out  of your App is ANSI SQL, your PB ODBC interface converts that to ODBC SQL and in turn the ODBC middleware converts that to T-SQL. The native ASE result set from ASE gets converted to an ODBC result set. Then the ODBC middlewre then converts that to an ANSI result set. In the native "ASE" connection ... your PB App sends T-SQL and handles the ASE result set native (no conversions). Food for thought.

    However, your ODBC connection to ASE should still work. Make sure that your SQLCA (aka transaction object) is set as follows:

  • SQLCA.DBMS = "ODB"
  • SQLCA.DBParm = ""

  

  Also note that you need to deploy the ODBC interface driver from PB (PBODB170.dll) and also the PBODB170.INI file as well with your PB Apps. his can be done automatically by using the PB Packager Utility that comes with PB2017 to create an MSI installation for you.

HTH

Regards ... Chris

  

 

 

Comment
bryan hui
  1. bryan hui
  2. Tuesday, 31 July 2018 12:17 PM UTC
Dear Chris,

Confirm from our colleague that we are using older sybase that we need to use ODBC.

Then I set our

clib.ini

"

Common Library]

DBMS="ODB"

Database=cust_service

UserId=

DatabasePassword=

LogPassword=

ServerName=TPC_BIGMAC

LogId=

Lock=

DbParm=

AutoCommit=1

logpass=

DBPass=

[logon]

userid=

password=

appnum=0

"

when object read info and connect.

It does not show error.

But it will prompt a screen for select datasource. Then I select one row on machine datasource page, it can proceed.



How can we avoid such popup and can connect that datasource directly ? I also include the printscreen on the ticket #8760.

please kindly advise

  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 31 July 2018 13:29 PM UTC
Sounds like your App may not be loading its Transaction Object's DBPARM field correctly. The values in the DBPARM field are used when connecting via ODBC. That is, they are passed to the ODBC interface driver for controlling the connection details and options (like suppressing pop-up DataSource dialogues).

Hopefully, your App logs the connection information in the Transaction Object when the connection fails so that you can try to determine the reason(s) why it cannot connect.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.