Issue 98150

Summary: target db tables are wiped out upon connection via Unix ODBC within OOo 3 - Base
Product: Base Reporter: floaiza <floaiza2>
Component: ReportBuilderAssignee: AOO issues mailing list <issues>
Status: UNCONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues, mechtilde
Version: OOo 3.0Keywords: needmoreinfo, oooqa
Target Milestone: ---   
Hardware: PC   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description floaiza 2009-01-16 15:34:50 UTC
OS = FEDORA 10 - GNOME
OpenOffice application = Base
Connection = Unix ODBC

Steps:

(1) Connect to Mysql and create a new target database running the corresponding
SQL script.

(2) Check the target db created in Step (1), e.g., execute "show tables"
command. Result shows all the tables have been successfully created.

(2) Create the ODBC connection using "ODBC Data Source Administrator" (the rpms
for the libraries required are those from MySQL website)

(3) Launch OpenOffice Base and create a database from an existing source. Select
ODBC and enter the user and pswd; test connection, and finish.

(4) Interface shows the database objects with "Forms" selected. Clicking on
Tables does not refresh the display, i.e., no tables are shown.

(5) Go back to MySQL and from the command line connect to the target db. 

(6) Execute "show tables" command. Now no tables are shown. This appears to be
the result of having connected with Open Office 3 Base to the target db via Unix
ODBC.
Comment 1 Mechtilde 2009-05-31 20:55:30 UTC
do you edit ~/.odbc.ini
what is the entry in /etc/odbcinst.ini

do you also try JDBC?
Comment 2 Rob Weir 2013-02-02 02:58:55 UTC
This Issue requires more information ('needmoreinfo'), but has not been updated
within the last year. Please provide feedback as requested and re-test with the the latest version of OpenOffice - the problem(s) may already be addressed. 

You can download Apache OpenOffice 3.4.1 from http://www.openoffice.org/download

Please report back the outcome of your testing, so this Issue may be closed or
progressed as necessary - otherwise the issue may be Resolved as Invalid in the
future.