Skip to Content
author's profile photo Former Member
Former Member

Problem with SQLAnywhere and ODBC

Problème with SQlAnywhere Sybase

Sur un Pc Windows 7 64bits, en PB12.6 il fonctionne dans le database painter, mais il ne fonctionne pas en run ou runtime.

Le message SQLSTATE=IM002

Microsoft ODBC Driver Manager Datasource name not found and no default driver specified.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Aug 18, 2016 at 01:52 PM

    Thank you Chris,

    There was actually a problem in the DBPARM=connectstring of the application. It was false!

    It is OK,


    PA

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 18, 2016 at 01:17 PM

    Hello,

    PB 12.6 IDE is a 32-bit process and can only communicate with 32-bit database drivers, meaning 32-bit client files.

    At runtime, you can generate and deploy either a 32bit EXE or a 64bit EXE.

    Depending on the bitness and if the EXE communicates with an ODBC datasource, you have to configure the proper admintool.

    For 32bit, you have to run the odbcad32.exe from the SysWow64 subfolder

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 18, 2016 at 01:35 PM

    -Le profil ODBC est bien référencé dans le ODBC32.

    -Dans le database painter de PB12.6, il n'y a aucun problème pour ouvrir la base SQLAnywhere et accéder aux différentes tables.

    -Par contre, lorsque je fais "run" pour visualiser l'application en développement je reçois le message :

    SQLSTATE=IM002

    Microsoft ODBC Driver Manager Datasource name not found and no default driver specified.

    -Le problème est identique en PB12.5.

    -Je rencontre ce problème depuis que j'ai changé de Pc de développement...

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 18, 2016 at 01:36 PM

    Hi Pascal;

    1) In the DB Profile Painter, you should be able to open up the SA ODBC profile. Then looking at the Preview tab page, you should see how the SQLCA transaction object is being set, as follows:

    2) You must now ensure that your PowerBuilder application uses similar coding to load the SQLCA transaction object properties as you would have seen in the DB Profile painter's preview.

    HTH

    Regards ... Chris


    pastedImage_0.png (25.3 kB)
    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.