To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=75442
------- Additional comments from [EMAIL PROTECTED] Wed Apr 4 21:07:45 +0000 2007 ------- No, it seems that 75442 is still a problem, ie ODBC connections to the same datasources as accessed via JDBC fail although the symtoms are now different. However all is not lost as there is definitely an improvement over previous OOo versions and testing I've done with UniVerse. As background - UniVerse supports 2 types of SQL "schemas" 1. a "true" SQL schema with Catalog defintions, triggers, constraints, views etc which are enforced by the DBMS and 2. a "free-form" "ACCOUNT" which enables the user to create non-SQL tables/files, and implement rules in client applications only (although triggers are also supported). (A third option also exists in that non-SQL tables can be created in SQL Schemas - used for speed eg hashed tables). However non-SQL files are "sqlised" on the fly by the ODBC driver as long as the dictionaries of these files have been massaged to make the data ODBC compliant and the Account is marked as accessible via ODBC. The symptoms are different when connecting to a SQL schema vs Universe ACCOUNT as follows: Connecting to "true" SQL Schema: I can connect to the data source but no tables are shown. Trying to select Query facilities, eg Create Query in SQL View does not enable me to access the database or create queries. This is unusual as, for example, "true" UniVerse SQL Schemas are more easily accessed via ODBC applications than UniVerse Accounts as the Schema and catalog take care of everything, ie there is no manual intervention required to make non-SQL tables accessible via ODBC. I have also tested that the username has been GRANTed the correct priveleges. Also, I do get the same error message as reported in 75442 when OOo crashes. Connecting to an UniVerse Account: The behaviour changes slightly here: While OOo does not retrieve/display the table definitions as for SQL Schemas, I am able to create a query in Create Query in SQL View and retrieve data from the table - however trying to then enter design view results in a message stating that the "CUSTOMER_MASTER" is not a table or a query. I have tried disabling schema and catalog names in Advanced Settings but that makes no difference. In an Account I can also access the facilities to create tables and the correct data types for columns is shown, which is not the case with the JDBC, although UniVerse disallows actual creation of the tables as SQL DML is not permitted in UniVerse accounts. In both cases (Schemas and Accounts) if I check on the server a connection has been made and a call to obtain the schema details is made. Regards Ian Stuart --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
