Bug #13230 | MyODBC 3.51.11 don't work with the tool CognosScript | ||
---|---|---|---|
Submitted: | 15 Sep 2005 16:04 | Modified: | 6 Oct 2005 11:44 |
Reporter: | Annabelle GERARD | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | Mysql 3.23.49 | OS: | Windows (Windows 2000) |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[15 Sep 2005 16:04]
Annabelle GERARD
[15 Sep 2005 16:36]
MySQL Verification Team
Are you tried the last MyODBC release 3.51.11-2?
[16 Sep 2005 7:43]
Annabelle GERARD
Yes, I try with 3.51.11-2 ODBC version and it doesn't work.
[16 Sep 2005 16:18]
MySQL Verification Team
Sorry but I was unable for to find at least a trial version of CognosScript for to test on our side. Could you please enter in contact with their support for analyze on that incompatibility you are experiencing. Thanks in advance.
[21 Sep 2005 15:39]
Annabelle GERARD
Ok we wait a response from Cognos but the problem seems to come from the function SQLDriverConnect in the ODBC driver. The liste of changes in the 3.51.10a explains the SQLDriverConnect was heavily reworked to more fully support prompting. CognosScript is very near Visual Basic. Can this change explain my problem ?
[21 Sep 2005 17:02]
Bogdan Degtyariov
Is there some way to edit the connection string for Cognos script? Seems the problem is in FLAG_NO_PROMPT option. To avoid the checking of a window handle it is needed to provide option=16 in the connection string or set "Don't prompt upon connect" option in MyODBC DSN configuration dialog.
[22 Sep 2005 15:31]
Annabelle GERARD
I tried a CognosScript macro with this command : Set objConnection = CreateObject("ADODB.Connection") strConnectionString = "PROVIDER=MYSQLProv" _ + ";location=xxx.xx.xx.xxx" _ + ";DATA SOURCE=" + DBNAME _ + ";USER ID=" + USER_ID _ + ";PASSWORD=" + PASSWORD + ";" objConnection.ConnectionString = strConnectionString objConnection.Open objConnection.ConnectionString Set oImpApp = CreateObject("CognosImpromptu.Application") oImpApp.Opencatalog CAT_PATH + "\CATALOGUE WATT STATISTIQUES.CAT", "util", "util" The database connection is ok but the same error appears during the opencatalog function. The option "Don't prompt upon connect" option in MyODBC DSN configuration dialog doesn't work more.
[23 Sep 2005 15:22]
Luc Michaud
If you have a safe environment, you may try to grant user ODBC (default ODBC user) with no password and for all host. grant all on *.* to `ODBC`@`%`; flush privileges If you need a secure environment, this solution is not good. You will have to find where the default ODBC user is used and replace it by a other user and password.
[6 Oct 2005 7:29]
Annabelle GERARD
I found the solution in my CognosScript macro : the function OpenCatalog has a parameter which specifies if the database is connected or not. So I put 0 for not connected to database and then i use the function connectdatabase (User Database, Password Database) which is normally prescribed if we use an ODBC connection !
[6 Oct 2005 11:44]
MySQL Verification Team
Thank you for the feedback, I am changing then for a not a bug.