Hi Andrew, > Perhaps I am not clear on what you mean by parseable. In the query > builder at this time ( ver. 2.0.2 & 2.0.3.dev bld 164 ) I can create a > select statement that does not need to run in 'SQL Direct' mode and does > use a parameter. However, it can* not* be opened in the designer.
That's two different things. Basically, our parser understands a certain set of SQL. If a statement can be parsed, then we can offer additional functionality like parameter support and the like. To open a statement in the graphical query designer, the designer needs to *fully* understand the structure of the statement. Parsing it is needed, but not sufficient for this. Or, let's say: The designer needs to know all SQL structures it could potentially encounter, and this is just a matter of constantly adding more knowledge to the designer. At the moment, it seems it is lacking a little knowledge about a few SQL features. So, if you have a query "SELECT * FROM inner_query ...", and both this statement and the inner_query contain parameters, they will all be recognized and used - as long as both statements are parseable. Whether or not the outer query can be displayed in the graphical query designer is not affected. > The query runs fine, the parameter is prompted for and replaced. The > query will not open in the designer ( I know a bug I suppose ). You should have read enough from me to know that I cannot resist saying: What's the issue ID? :) Thanks & Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
