Search found 2560 matches
- Thu Apr 25, 2024 4:11 pm
- Forum: 3rd party products
- Topic: ReportPro 2.40 for X#: empty report while showing correct in VO ReportPro 2.31
- Replies: 10
- Views: 489
- Thu Apr 25, 2024 9:18 am
- Forum: 3rd party products
- Topic: ReportPro 3.60 for XSharp 2.60 memory exception
- Replies: 12
- Views: 448
Re: ReportPro 3.60 for XSharp 2.60 memory exception
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 ho...
- Thu Apr 25, 2024 8:33 am
- Forum: 3rd party products
- Topic: ReportPro 3.60 for XSharp 2.60 memory exception
- Replies: 12
- Views: 448
Re: ReportPro 3.60 for XSharp 2.60 memory exception
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 ho...
- Thu Apr 25, 2024 8:12 am
- Forum: Product
- Topic: X# 2.18 EnableCellDraw FIELDSPEC:VAL error
- Replies: 5
- Views: 311
Re: X# 2.18 EnableCellDraw FIELDSPEC:VAL error
Hi Michal, OK, that's good to hear! I also found a workaround for the EnableCellDraw() problem in 2.18, please add this method in your ColorColumn class and it should work fine now: OVERRIDE METHOD __DrawCellData(hDC AS PTR, iX AS INT, iY AS INT, dwOptions AS DWORD, ptrRect AS PTR, ; pszData AS PSZ,...
- Thu Apr 25, 2024 7:41 am
- Forum: Product
- Topic: X# 2.18 EnableCellDraw FIELDSPEC:VAL error
- Replies: 5
- Views: 311
Re: X# 2.18 EnableCellDraw FIELDSPEC:VAL error
Hi Michal, Thanks, I see the problem with 2.18, although this does not exist in 2.19 and our current version either. Apparently it was something that was fixed later, but not sure what, will have a look into it and see if there's a workaround for 2.18. In the meantime, can you please temporarily dis...
- Tue Apr 23, 2024 10:57 am
- Forum: 3rd party products
- Topic: ReportPro 3.60 for XSharp 2.60 memory exception
- Replies: 12
- Views: 448
Re: ReportPro 3.60 for XSharp 2.60 memory exception
Hi Michal, Those RP3 errors seem very strange to me, can't explain them easily, maybe there's some kind of dll hell. In any case, X# 2.13 is very old, released almost 2 years ago I think, so it's much better to install a newer version. Not sure if this will fix the problems, but it's quite possible....
- Tue Apr 23, 2024 10:51 am
- Forum: Product
- Topic: Miscellaneous questions about converting VO code to X#
- Replies: 43
- Views: 2207
Re: Miscellaneous questions about converting VO code to X#
Hi Kees,
Yes, String2Symbol() is a good workaround, but I think the compiler error with #NULL_DATE is a bug, will open a report about it, thanks!
Yes, String2Symbol() is a good workaround, but I think the compiler error with #NULL_DATE is a bug, will open a report about it, thanks!
- Tue Apr 23, 2024 9:40 am
- Forum: 3rd party products
- Topic: ReportPro 3.60 for XSharp 2.60 memory exception
- Replies: 12
- Views: 448
Re: ReportPro 3.60 for XSharp 2.60 memory exception
Michal,
Which exact RP3 version are you using?
Which exact RP3 version are you using?
- Tue Apr 23, 2024 9:36 am
- Forum: Product
- Topic: Open DBF’s not visible in BackgroundWorker second thread.
- Replies: 9
- Views: 380
Re: Open DBF’s not visible in BackgroundWorker second thread.
Roland,
In addition to what the guys said, did you also see this reply https://www.xsharp.eu/forum/topic?p=29495#p29495
In addition to what the guys said, did you also see this reply https://www.xsharp.eu/forum/topic?p=29495#p29495
- Tue Apr 23, 2024 9:34 am
- Forum: Product
- Topic: Miscellaneous questions about converting VO code to X#
- Replies: 43
- Views: 2207
Re: Miscellaneous questions about converting VO code to X#
Hi Kees, SYMBOLs do not need to be declared anywhere, they can just be used as literals anywhere in the code. For example this is perfectly valid code: FUNCTION Start() AS VOID LOCAL s AS SYMBOL s := #TEST IF s == #SOMETHINGELSE ? "something else" ELSEIF s == #TEST ? "test" ENDIF...