To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=110190
------- Additional comments from ia...@openoffice.org Fri Mar 19 15:00:07 +0000 2010 ------- The problem seems to be slightly different in DEV300m75 - I will do more testing in this regard. For completeness below is documented a more detailed ( I hope) description of the problem. The driver is IBM's JDBC driver for UniVerse - many thanks again to Frank Schonheit for helping to resolve some of the issues with this driver. To explain what is happening I'll compare what happens when a "standard" query created in Query Design is run versus what happens when generating a report via the report wizard. Query in Design View When using "normal" query builder the SQL that is generated refers to the column names provided by the database. When the data is loaded into a spreadsheet or datasource window the column headings are replaced by the column labels stored in the dictionary of the table - this is all good because cryptic table column names are replaced by the more meaningful labels. For example - the following query runs just fine SELECT "ACC", "FM_DESCRIPTION", "FM_M1_TY", "FM_M2_TY", "FM_M2_TY", "FM_M3_TY", FROM "COAM" The column labels for columns FM_M1_TY, FM_M2_TY , FM_M3_TY etc are October, November, December etc. The column names are replaced in the result by these labels. The labels are derived from the metadata provided by the database schema. However when creating a report using the report wizard and basing the report on an existing query the available fields in the query are shown using the label names (instead of FM_M1_TY October is shown). This in itself is not a problem if the SQL that is generated and executed later referred to the column names. Then, when you are presented with the dialog where you can define the labels for the columns, the label (eg October) is shown and not the column name - still not a problem and makes sense to use the column label instead of the column name. Further dialog (eg grouping, sorting ) also refer to the column label instead of the column name - makes sense to me so far. However when executing the report the SQL is generated using the column labels i.e SELECT "ACC", "FM_DESCRIPTION", "October", "November", "December", FROM "COAM" which results in an error from the database when trying to execute the query as there are no columns named October, November, December Hope this makes sense. Rgds Ian --------------------------------------------------------------------- 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: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
