Issue 118014

Summary: ODBC regression between 3.3 and 3.2
Product: Base Reporter: stacy
Component: codeAssignee: AOO issues mailing list <issues>
Status: UNCONFIRMED --- QA Contact: RottenEogat <RottenEogat>
Severity: Normal    
Priority: P3 CC: frank.schoenheit, info, issues, r4zoli
Version: OOo 3.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
OOBase 3.3: Tables List, successful result
none
Error-Message after try to open table content (data) none

Description stacy 2011-05-13 15:51:51 UTC 
I've been using Base to connect via ODBC to our ERP database.  I use Base as a front end to our actual database.  I've registered the .odb file.  We use an older version of Fourth Shift (driver version 6.98.04.19) which is accessed across our LAN on a Windows Server 2003.  Works fine in version 3.2.  I've seen similar though not identical bug reports (3860 for example)  Client PC is running XP SP3

In version 3.3 I can log in to the database and see the tables but any attempt to view the tables results in the message "The data content could not be loaded. [Microsoft][ODBC Driver Manager] Driver does not support this function."  The same error message results when attempting to run queries.  The error message is "SQL Status: IM001"

I am able to successfully connect and use an Access database from version 3.3 without problems.  Turning connection pooling on or off appears to have no effect.

I have had to revert back to version 3.2 pending some sort of fix.  Critical functionality for me.  Happy to provide any logs if needed/possible.
Comment 1 r4zoli 2011-05-13 18:37:46 UTC 
Please try OOo 3.4 Beta, in it solved several bugs.

Changed componenent.
Comment 2 Frank Schönheit 2011-06-09 08:17:02 UTC 
reproducing this here will be difficult (well, impossible :-\ ), since your setup is ... well, we don't have it :)

You might want to turn on ODBC logging in the control panel, then attempt to open a table in OOo, then turn the logging off, and provide the log file here (beforehand, check the log doesn't contain data you do not want to expose to the public). This would help seeing which function fails.
Comment 3 smw-p 2012-02-13 15:55:00 UTC 
Created attachment 77216 [details]
OOBase 3.3: Tables List, successful result

Hello, I have The same problem changing OOBase 3.2 to 3.3 (or 3.4). The problem exist in LibreOffice V3.3/3.4 too.

We test it on a WIN-XP System (SP3) togehter with ODBC-Driver Acu-XDBC 8.1.3 from MicroFocus (Database = Vision4). 

Because our database works very well in connection with the other reference application MS-Access 2003/2007/2010 or with OOBase 3.2 too (or earlier), I am quit shure, that the problem is generated by OOBase 3.3 and 3.4 themselves.

Effects: After connecting the Database using the ODBC driver the tables list is shown correctly (see tables list). 
But klicking on the table symbol, I get - instead of the data of this table - an error message: 
-> "data could not be loaded, [TOD][ODBC Driver]UNFETTYP] unknown fetch type"

I have testet a lot of various possibilities, but without success. I think it's a bug.

Answers? Many thanks!

Peter
Comment 4 smw-p 2012-02-13 15:59:59 UTC 
Created attachment 77217 [details]
Error-Message after try to open table content (data)

Hello, I have The same problem changing OOBase 3.2 to 3.3 (or 3.4). The problem exist in LibreOffice V3.3/3.4 too.

We test it on a WIN-XP System (SP3) togehter with ODBC-Driver Acu-XDBC 8.1.3 from MicroFocus (Database = Vision4). 

Because our database works very well in connection with the other reference application MS-Access 2003/2007/2010 or with OOBase 3.2 too (or earlier), I am quit shure, that the problem is generated by OOBase 3.3 and 3.4 themselves.

Effects: After connecting the Database using the ODBC driver the tables list is shown correctly (see tables list). 
But klicking on the table symbol, I get - instead of the data of this table - an error message: 
-> "data could not be loaded, [TOD][ODBC Driver]UNFETTYP] unknown fetch type"

I have testet a lot of various possibilities, but without success. I think it's a bug.

Answers? Many thanks!

Peter
Comment 5 smw-p 2012-02-13 16:01:25 UTC 
(In reply to comment #4)
> But klicking on the table symbol, I get - instead of the data of this table -
> an error message: 
> -> "data could not be loaded, [TOD][ODBC Driver]UNFETTYP] unknown fetch type"
Comment 6 r4zoli 2012-02-14 07:11:10 UTC 
We don't have your setup, please use ODBC logging as suggested in comment #2, to reveal more data.
Comment 7 Oliver-Rainer Wittmann 2012-06-13 12:17:28 UTC 
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.