Hi Frank, I hope you had a wonderful and relaxing vacation.
Alright, I'll go ahead and open an issue then. FYI - I have tried a couple of other mixes here. Using the latest MSO12 OLE DB drivers to connect to both the MDB file and them same data as an ACCDB formatted file. Using Access 2007 to do the conversion. - the results are the same. ( well, not identical but close enough in this specific case ) The last test I want to run is to recreate the test database - but this time not use the lookup field feature in the table definitions. That has been known to cause some problems according to a couple of postings I found at some Access support boards. I am afraid that won't be much comfort to anyone that has to work with an existing database - but just in case. Finally - I will be opening at least two issues as I have found a couple of new problems. These are in the Sun Report Builder trying to use these tables - it seems that when the QiQ feature is used some of the columns are returned with names such as Table.Column, example: Orders.OrderID It appears that the driver is doing this only when the query would include both columns used to join two tables, actually returning only one column then and telling the user which table it came from. This is fine until you try to use one of these columns to group on in the SRB - then an error is issued and the report fails to run. The actual error code and message is: SQL Status: 3125 Error code: -2147467259 '' is not a valid name. Make sure that it does not include invalid characters or punctuation and that it is not too long. Next is the problem with creating a query from SRB - if you do this then you can't turn escape processing off in the designer and when you try to save it back and return to SDB - bam the problem hits. So you have to create the queries prior to starting the report, or switch back to the ODB window to launch the designer. Then even if you do create a query with EP off, but then in the SRB forget to set Analyze SQL Command to NO - well you guessed it. Finally - the problem I mentioned in an earlier post about the Query designer not showing all columns in a Sub query. It seems this is related to the 'smart' behavior regarding the two columns with the same name feature. It appears that the missing column name is always the one directly after one of these Table.Column names. LOL - not very clear there, I'll attach a file with an example to the issue. Well, that's it for the moment. On 8/19/07, Frank Schönheit - Sun Microsystems Germany < [EMAIL PROTECTED]> wrote: > > Hi Andrew, > > > I haven't found an Issue dealing with this so I suppose I will go ahead > and > > open one. > > Please do so - we talked about the need for performance data already :) > > (And yes, the respective thread still waits for some answers of mine - I > still have some backlog to clear and too little time to spend for it, > sorry.) > > Ciao > Frank > > -- > - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - > - Sun Microsystems http://www.sun.com/staroffice - > - OpenOffice.org Base http://dba.openoffice.org - > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
