The fix that you sent (cwbodbc.dll) has fixed PMR 66067-- Thanks! I assume it will also be included in the next CA Express V4R4 service pack, so that we will not have to worry about upgrading int he future? Also, please note 28556 should remain open- this is unrelated to this fix. Regards, Luther -----Original Message----- From: firstname.lastname@example.org <email@example.com> To: Mark Ebling <mark.ebling@HYPERE.COM>; Luther Ananda Miller <luther.miller@HYPERE.COM> Date: Thursday, 14 October 1999 13:13 Subject: PMR 28556 >Luther/Mark, > >We have had a reply from the developers on the abovementioned PMR : > > 'After some discussion with other ODBC specialists and some > development involvement please see SA85355. I have attached > the testfix for this apar to ISTWORLD as a response to your > entry so you should be able to get the testfix. > > Now more importantly I need you to point the customer to the > SQL Reference. Chapter 2 talks about Language Elements. > Under the section labeled Tokens you will find a paragraph > about 'spaces'. This very explicity states that tokens must > be followed by 'space'. For this reason I would recommend to > the customer avoid leaving the spaces out in his application. > Essentially the customer is counting on the ODBC parser to > handle this correctly. There is no guarantee that we will > always handle cases like this correctly in our parser. > The suggestion is just to make the customer aware and > hopefully avoid any future problems for the customer.' > >This testfix is for file CWBODBC.DLL. >We recommend that you take the following steps: >1. Rename your current copy of CWBODBC.DLL to perhaps CWBODBC.OLD, >2. Detach this copy of CWBODBC.DLL to your PC. >3. Reboot the PC >4. Retest the problem. > >Following is the problem description for SA85355 : > > ERROR DESCRIPTION: >The Client Access Express ODBC driver will incorrectly report > the SQL statement type as 'Other' when the statement used TAB > characters to delimit the tokens rather than spaces. This > results in an error when the prepared statement is executed. > The error reported on the PC is MSGSQL0518 Prepared statement > not found. This is a problem in the token parsing so using > spaces in the SQL statement rather than TABs will circumvent the > problem. > >. >Please advise the outcome of this testfix. > >Many thanks.......... > > > > >(See attached file: cwbodbc.dll) > > Regards > Barbara Bungate > Software Service Specialist - IBM Support Centre > IBM Australia Limited, 55 Coonara Avenue, West Pennant Hills NSW 2125. > > Phone 61-2-9354-4514 Fax 61-2-9894- 0856 > BUNGATEB@AU1.IBM.COM > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.