Page 1 of 1

TQRChart

Posted: Tue Dec 16, 2014 8:32 am
by 16470794
Hello,

I am using:

-Delphi XE7 pro
-TeeChart pro 2014 VCL XE7 (no sourcecode)
-Quickreport 5.06 for Delphi XE7

I followed the instructions to recompile TQRChart but without success.
In the instructions (Install.pdf):

For example in point 13: I fetch Tee9QR5D19.dpk not from Teechart installation folder but from QR Installation Folder.
After all, Delphi XE7 did not accept DclTeeQR5D19.bpl as a new package (saying: not installed in the system).

Can you help?

regards

Re: TQRChart

Posted: Tue Dec 16, 2014 9:17 am
by 10050769
Hello Reinhard Hagen,

Attached you find the TeeChart Pro for Quick Report 506 packages for Delphi XE7.
Please follow the instructions below to build them:
- First of all, make sure the TeeChart component and the QuickReport components work fine, alone, in a new simple example project.
- Build the Tee9QR506D21 package and make sure the compiled files are in a known "compiledWin32" folder to find them later.
- Build the DclTee9QR506D21 package and make sure the compiled files are in a known "compiledWin32" folder to find them later.
Only in the case you want compile in Win64, too.
- Build the Tee9QR506D21 package and make sure the compiled files are in a known "compiledWin64" folder to find them later.
If you find problems to build any of these packages, take a look at the QuickReport instructions here.
Once you have both packages built, copy the packages from the "compiledWin32" folder accordingly:
- DclTee9QR506D21.bpl to $(BDS)\bin
- Tee9QR506D21.bpl to %windir%\SysWOW64 (if a 64bit OS) or to %windir%\System32 (if a 32bit OS)
- The rest of the files from the "compiledWin32" folder to $(BDS)\lib\win32\release and $(BDS)\lib\win32\Debug
Only in the case you want compile in Win64, too.
- Tee9QR506D21.bpl form compiledWin32 folder to %windir%\SysWOW64
and
- Tee9QR506D21.bpl form compiledWin64 to %windir%\System32.
- The rest of the files from the "compiledWin64" folder to $(BDS)\lib\win64\release and $(BDS)\lib\win64\Debug
Then you should be able to open the IDE, add the $(BDS)\bin\DclTee9QR506D21.bpl package to the components list in the IDE and use it.

If you still find problems with it, please don't hesitate to let us know.
Tee9QR5D21.zip
(1.28 MiB) Downloaded 883 times
Hoping it will help.
Thanks in advance,

Re: TQRChart

Posted: Tue Dec 16, 2014 11:37 am
by 16470794
Hello,

thank you very much!! The Tee9QR5D21.zip is wht I needed.
But now, when I compile Tee9QR5D21.dpk then I get the error message:

[dcc64 Fehler] E1026 Datei nicht gefunden: 'Tee9QR5D21.otares'

Can you again help please?

regards

Re: TQRChart

Posted: Tue Dec 16, 2014 3:36 pm
by 10050769
Hello Reinhard Hagen,

I would like suggest you disable the unit scope names to solve the problem you are experiencing. To do it, please, follows the steps below:

1- Open the Tee9QR5D21.dpk project.
2- Go to the project menu->Options->Unit scope name -> inherit and disable the option.

Then you should be able to compile the TeeChart Pro for Quick Report without problems.

If the problem persists, please let me know.
Hoping it will help.
Thanks in advance,

Re: TQRChart

Posted: Mon Mar 23, 2015 6:18 am
by 16470794
Hello Sandra,

thank you, so far so good.
When I create a new Project with Delphi xe7 with a QuickReport component and an embedded QRChart, everything works fine.
But, when I try to compile the 'old' Delphi 2007 project with similar situation ( QuickReport component with an embedded QRChart) then the following message appears (in german):

[dcc32 Fataler Fehler] QuickRpt.pas(6911): F2051 Unit QrTee wurde mit einer unterschiedlichen Version von QuickRpt.TQRPrintable compiliert

In english:
[dcc32 fatal error] QuickRpt.pas(6911): F2051 Unit QrTee was compiled with a different version of QuickRpt.TQRPrintable

What can I do?

Thank you for your help!!

Regards
Reinhard

Re: TQRChart

Posted: Mon Mar 23, 2015 7:58 am
by yeray
Hello Reinhard,

Here it is a detailed explanation about how the paths in the IDE should be.
When new projects work fine but an old still gives compiler errors like yours, it usually indicates the old project has some path hardcoded referencing some previous installation of the component. To correct that, I'd suggest you to edit (with notepad or similar) the project files and fix manually any wrong reference you may find on them.