Fast Query Builder???
I have bought fr4 pro (including FQB) for delphi 2009 and installed it but cannot see how to run the query designer. There is no component anywhere, the sql properties of my queries on my data page have nothing but a plain editor. There are no instructions that I can see. nothing in the program group, just a load of files placed in the C:\Program Files\FastReports\FastQueryBuilder folder.
I bought the pro because of this tool. How on earth do you get it to run?
(an old thread from member 45 in 2003 said
"assuming you have an internal db engine set of components installed, add your query component to the data page, click on the sql prop in the oi in the sql edit dialog click on the querybuilder button. "
but that does not seem to work as the sql properties do not contain a query builder button)
Howard
I bought the pro because of this tool. How on earth do you get it to run?
(an old thread from member 45 in 2003 said
"assuming you have an internal db engine set of components installed, add your query component to the data page, click on the sql prop in the oi in the sql edit dialog click on the querybuilder button. "
but that does not seem to work as the sql properties do not contain a query builder button)
Howard
Comments
I must say its not exactly obvious though!
Its a handy tool but I couldn't see how it could be useful. I had a query component in my data page (delphi. not FR) to which my report was connected and was working OK. To try out FQB I added another report but although I could re connect to my database I couldn't seem to connect my report to the sql I had just designed, only to the original delphi adoquery.
It would have been nicer if it was a stand alone tool allowing one to design and test some sql before building it into the delphi code. as it is it seems just as easy to design/test using ms access and then copy the sql over.
unless I am missing something? I use fr to link to a delphi adoquery whose sql I insert dynamically as buttons on a form are clicked. It seems that the fqb is more for situatuions when the report source is hard coded.
Howard