I split my original project on several bpl's files, then I started to have the error when I convert a grid to a excel file.
Steps to Reproduce:
compile the project on zip file
Actual Results:
don't convert grid
Expected Results:
convert grid
We have closed this ticket because another page addresses its subject:
Possible bug in ExportGrid4ToExcel - "Unsupported export type"
Hi,
You will find the information on this problem in the related report DQ13721.
Thanks,
Serge
Don't work, when I eliminate dx files from runtime packages I recive the error: "a class named TCustomdxGraphicReportLink already exists", there are others modules on other bpls linked what use dx files,
I apreciate any other suggestion
Hi,
Basically, the way to resolve such problems is described in the following Knowledge Base article:
"How to avoid the "A class named AClassName already exists" error when using DLLs in your applications"
Article ID: A1994 (https://www.devexpress.com/kb=A1994)
However, this approach is not used for the ExpressPrinting System because it has a serious limitation: The packages of its ReportLinks are not split into design- and runtime parts. Thus, it is strictly prohibited to include its packages in the list of runtime packages when compiling your projects. As the most complete way out, we recommend that you keep both the Printing System's core and ReportLinks only in the main module of your application.
Thanks,
Serge
Thanks, but the module is on main module, if you check the sample that I sent you you can see that. any way my problem is with ExportGrid4ToExcel not with ExpressPrinting System like I told you in my first message and sent yout the zip file so you can test it and see the error,
thanks in advance
Hi,
Yes, I do understand that the problem relates to the Grid's export. But whether the solution from report DQ13721 helps you resolve this particular issue or not (not relating to the message regarding the ExpressPrinting System's packages)?
Thanks,
Serge
solution from report DQ13721 didn't solve my problem.
when I applied this solution it gave me the next error: "a class named TCustomdxGraphicReportLink already exists".
thanks
Hi,
I seem to have found the cause of the problem. Add the cxExportVCLC6 package to the list of runtime packages in your original sample. This way, the problem disappears in our tests.
Thanks,
Serge
By the way, this suggestion is mentioned in report D537 … to which my original responses refer.
Thanks,
Serge
I don't have acces to D537 but the solution add cxExportVCLC6 to package list WORK!!!
thanks a lot!!!
Thank you for informing us that the problem is resolved. I am glad that our assistance was helpful. Please feel free to contact us in case of any difficulties. We are happy to help you at any time.
Thanks,
Serge
P.S. I have published report D537. Sorry for the confusion.