I'll try it out hopefully next week, got a lot of other work lined up at this time.

Memory corruption issues can be like that, when running through the debugger some memory locations may be different, preventing the underlying problem to expose itself. What OS are you using and what is the .Net Framework version installed? Also since I don't have your email address, can you please ...

Hi Michal, Thanks for the very good sample, but unfortunately I could not reproduce the problem here, all 65 pages are always printed ok here. Does the problem happen with any printer driver? Even when selecting a pdf driver, like PDF creator or Microsoft's print to pdf driver from Windows? To be ...

Great, it works, thank you, Chris.

Chris wrote: ↑Thu Apr 25, 2024 7:41 am In the meantime, can you please temporarily disable the EnableCellDraw code and check if everything else works fine for you with 2.18?

Yes, already did that. So far everything else works without issues, just have to sort through a hefty heap of new warnings.

Upgraded to X# 2.18, new findings: - I managed to make ReportPro3 run with DBFs - we simply tried to push a CDX dbf into a report which expected MDX, so that's on us. - The exception happens regardless of what type of data source is used. - The exception happens when printing directly from ...

After upgrading from X# 2.13 to 2.18, DataColumn:EnableCellDraw stopped working with the following error: Error message: -------------- Description : cString is not of type STRING Subsystem : Database GenCode : EG_ARG Argument error FuncSym : VAL Severity : ES_ERROR Can Default : False Can Retry ...

It's this one: ReportPro 3.60 for XSharp 2.60 Now I'm thinking, our X# version is 2.13, so we should be using ReportPro 3.54 for XSharp 2.10 ? If that's the case, then there is a different exception it gives at start: Application: ReportPro3.exe Framework Version: v4.0.30319 Description: The process ...

Back when we started with ReportPro3 X#, we never managed to make it run with DBFs. Trying to add a DBF section ends with following exception: Application: ReportPro3.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: XSharp.Error ...

I managed to reproduce it inside ReportPro3 itself. I've created an SQL table with a single integer column and populated the table with at least 1000 rows. Then I created a new report (A4 format, metric system, portrait/landscape doesn't matter) and added a single field inside the body with binding ...