Hi, all.
 
Tony wrote:
What is going to happen with this heep of dog dung.
 
QR version 3 with Delphi 4 is the most buggy heep of rubish I have ever come accross. Surly one can expect it to be reasonably clean a year ofter release?
Yes, you would think so. Sadly, ...  
I don't know about the rest of you, but I am really annoyed to have to put up with this crap considering the price I payed for version 4 Client server. ie Having payed a professional price, I expect a professional product.
 
Surley there are others out there just as annoyed as me?  
Oh, yes. QR is one of the worst codebases I've seen in a _long_ time. I hate the thing with a passion.
Yes I do have the latest QR update.
Yes I have swapped to Report Builder Pro, but there is still a lagacy of 3 years worth of QR effort out there for me to consider. 
Yeah, we've switched to RPPro for all future work but we're stuck with some legacy QR stuff which we are in the process of replacing via a complete rewrite. Boy, will I be SOOO happy once that's done! 
 It is quite impossible to communicate with QR.
Yup. I've sent them bug reports with the necessary bugfixes attached. No response, no bugs fixed so I just gave up and kept patching them myself. I've lost count of the number of bugs fixed or worked around now... It ain't pretty in there. Admittedly, I've been working with their QRDesigner interface which is _really_ bad but even the TQRPrintables are 'quirky' (for want of a polite term) at best.
Each version of QR has gotten progressivly worse.
Hrmm, ain't that the truth. Tony, I have a version of the QR 2 codebase that has been patched (by me)and works with Delphi 4. That at least avoids all the bugs they added in QR 3. Provided you have a source license for the full QR, I don't see any legal reason why I couldn't supply you with a copy of that. Drop me a line if you think it might help.
What can we do to get these Vikings of their A's and get something happening about it?
 
Got your ears on Annie - Ray? 
Knowing how these bundling deals are sometimes done, the problem may be that Borland/Inprise paid a lump-sum licensing fee to the QuSoft people rather than a per-copy royalty style license. As such, the QuSoft people have no real incentive to fix the hard problems (which require a significant redesign and reworking IMO) since there is no more money in it for them.
 
TTFN,
  Paul.
 
 
 

Reply via email to