Fast Report with Rad Studio XE2
i'm just installed Rad Studio XE2 and i run fast report designer perfectly,
but after a few edition after i have an error message preventing to edit the report :
cannot find class TfrxReport
if i create a brand new report it works once and them i've got again the message.
any suggestions ?
thanks
but after a few edition after i have an error message preventing to edit the report :
cannot find class TfrxReport
if i create a brand new report it works once and them i've got again the message.
any suggestions ?
thanks
Comments
This code hides TfrxReport from FierMonkey and for some reason
"FindClass" function can't find for TfrxReport class when you're loading
report(only in IDE).
If you can't load report or get similar error with "Couldn't find
TfrxReport" message, put this
http://www.fast-report.com/pbc_download/LibD16.zip files to "Fast
Report\LibD16" dir (replace all).
I build and link without problems. When the app runs, I get this error about TfrxBarCodeView:
Project binContentExplorerXe2FastReportBarcodes.exe raised exception class EClassNotFound with message 'Class TfrxBarCodeView not found'.
So I took the barcode out of the report, now the report is empty, and the app runs fine. Now I tried to make the report be something other than blank. I added
the title band and the master row band, and one text field. The report ran ONCE and the second time, I got the same error as the other guys above.
This gives me a NOT VERY HIGH QUALITY feeling about Fast Report..... I was going to buy full version. I hope that this bug is fixed.
Warren
All the internet No subjece for this problem ,Today I Found It .
Thanks GPI .
I'am chinese
Not Good at Enlish.
I myself have had very little time with Fast Reports, mostly with the evaluation version. During that time, I dropped in a TfrxBarCodeView in the trial version and ran the application I created to invoke the report. No error. After the company I worked for invested based on my recommendation, I now get this same error with the application whereas I didn't before.
Your advice\answer falls a little short for me however very much appreciated. In the designer, I only see TFrxBarCodeView, not TfrxBarCodeObject.
In the Faq.txt I got with the product, I see the following similar advice. However doing a search on my hard drive for TfrxBarCodeObject I found the faq.txt
so having this answer on the web was good, put me closer to "my answer". haa, haa. Thank you.
Having said that, I do believe in a new version this issue can be remedied. Obviously in this answer below, taken from the faq.txt, dropping the TfrxBarCodeView doesn't register the component with the project. However adding the right pascal file to the uses clause does work.
============================================================================
Question: During compilation of the project, a message shows ??? Class TfrxButtonControl not found'.
Answer
Add the component TfrxDialogControls (TfrxRichObject, TfrxCrossObject, TfrxOLEObject, TfrxBarCodeObject, TfrxCheckBoxObject, TfrxGradientObject, frxChartObject, TfrxADOComponents, etc.) from FR component panel into the project or add in the uses section the following modules: frxDCtrl, frxRich, frxCross, frxOLE, frxBarcode, frxChBox, frxGradient, frxChart, frxADOComponents.
=============================================================================
Fast Reports worked predictably in their trial version which they didn't do the same in their registered version. When dropping this component down
from their designer such as the BarCodeView object, "frxBarcode" is not in the "uses" clause list of the project where it has to be registered. Normally dropping components into forms... the registration automatically takes place. In this case the designer drops components indirectly into the project's form (visible to the designer but not to the Delphi form).. but the code is there. Just have to "View as Text" on the form. So I had success simply by adding in frxBarCode to my uses clause.
This issue happens in the Team edition of Fast Reports 4.12.1
For continuity purposes as other objects this does work, like TfrmMemoView, why should bar codes object be the exception? Predictable functionality is what the end user like myself is looking for. Manually registering some objects while not having to do others isn't consistent. Users look for patterns. The more predictable it is, the better we like it.
It's a small oversight more than anything else as I see it. I guess in doubt, safe to drop these extra classes in the form to be on the safe side.
However in summation Fast Reports is a great product. With our comments it will get even better.