Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

ODBC vs ADO connection - Little lost here !

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ODBC vs ADO connection - Little lost here !

    lucstyves wrote: > My problem : Doing such a simple SQL statement never ends up > successfully if I try it with the ADO connection. But if I try the > ODBC connection, it works ! The only things having all this fail is > the SUBSTR embedded function. Do you receive an error message? What does it say? Can you turn on the tracing facility? Bill

  • #2
    ODBC vs ADO connection - Little lost here !

    Yes I receive an error message. The error message says that ",1" is not an expected SQL function. It is really the ADO connection that does not support my SUBSTR function. As soon as I remove the SUBSTR and replace it by the whole field, it works. Luc

    Comment


    • #3
      ODBC vs ADO connection - Little lost here !

      Thanks Michael but no luck, I already tought of using the SUBSTRING function instead of the SUBSTR. Same result. It really seem like if ADO connection would not support all SQL functions...... Anyone can confirm ? If anyone could tell me "I had the same issue and it seem like ADO is not supporting all SQL functions" than I would stop my research. But if someone would tell me "Nope. Only the connection mode is different but your SQL syntax will not be interpreted in any way and all functions should be supported" than I will continue scratching my head... Luc

      Comment


      • #4
        ODBC vs ADO connection - Little lost here !

        lucstyves wrote: > Yes I receive an error message. The error message says that ",1" is > not an expected SQL function. It is really the ADO connection that > does not support my SUBSTR function. As soon as I remove the SUBSTR > and replace it by the whole field, it works. The next 2 things to ask are: Are you on the latest version of Microsoft's MDAC? Are you on the latest Client Access Service Pack? Bill

        Comment


        • #5
          ODBC vs ADO connection - Little lost here !

          Yes I am. Latest Client Access Service Pack for version V5R3 and MDAC 2.8 updated on the internet. So based on the answer I had, nobody confirm me that ADO connection should support all SQL functions but nobody told me it should. I guess I'll stay with ODBC...... Until someone from IBM claim it should work. Luc

          Comment


          • #6
            ODBC vs ADO connection - Little lost here !

            Hi guys and gals ! I tried the following code. Notice that my first connection string is commented out since the second one is working and the first one is not. My problem : Doing such a simple SQL statement never ends up successfully if I try it with the ADO connection. But if I try the ODBC connection, it works ! The only things having all this fail is the SUBSTR embedded function. Maybe I am not using SQL statement correctly in an ADO connection, or maybe ADO is not supporting all SQL functions. Now I do not mind using an ODBC driver connection instead of ADO but still, if my problem is because of ADO not supporting all SQL functions, 2 questions remain unanswered. 1) Why does every publications seem to be saying ADO is the new connection that eveyone should use ? 2) Why is my second test working, even thus I am still using ADODB class, Command properties and Recordset for feeding the SQL and running the whole thing even thus I am now using an ODBC driver connection ??? Please bring light ! Thanks ! Luc St-Yves
            Code

            Comment

            Working...
            X