Frank found an unusual way to solve the direct issue. He found out that the dbf was only reported missing for instances after the first in the section tree. He solved it by changing: AAdd(aSwap, {"Laadlos3",,,,, oDBLaadlos}) to AAdd(aSwap, {"Laadlos3",,,,, oDBLaadlos}) AAdd(aSwap...

We have a weird ReportPro (VO 2.31) problem for which I give multiple details in case they are related. From the X# program (using ReportPro 2.40) the program asks for a missing dbf which is not missing. Besides, that (long unchanged) report now shows much delayed from the VO based program. What hap...

For future readers: the report constructed a file name in an expression within the Picture Tool. This does not work using Bitmap or File Name returned from an Expression giving an error in the designer (not sure why not), so apparently the original designer changed the option to Directly from File. ...

Hello Chris, The picture directory is D:\kl29\rpt\bmp. You are right about the parenthesis, indeed weird that VO accepts this: "UN "+Imco.Unnummer+" "+lTrim(Alltrim(iif(IMCO.Taal=="NL",Un.Taalnl ) , iif(imco.Taal=="DU",Un.Taalde,Un.TaalUK)))) should be: "...

In the meantime I have found out that the picture link points to a valid and present picture file, without anything illegal in the path name. So I better send the report to you to check (why it works in VO and not in X#) Besides a similar problem exists with another report. This has a trigger with a...

Indeed. I used the Search option in the main screen. This gives only 3 results. I'd say it should give the same result.

Dick

Hello Hansjörg,

I know; I meant that the keywords Power+Tools didn't bring up this page (anymore) in this forumsite.

Dick

Hello Robert, Chris, I opened the report with a hex editor and indeed there's a picture reference in it. Frank has to check it (Friday) as it refers to their server. If that's the cause indeed, it leaves 3 questions: 1 Where the picture can be removed or changed, in the ReportPro editor. I don't see...

In a ReportPro 2.40 installation, opening a report gives a runtime error Illegal characters in path error This path is valid (copying the report to something like c:\temp and opening the report there gives the same error). When we open the same report from the VO's ReportPro 2.31, there is no proble...

In 2022 we had this discussion and when talking to Kees I found out that he wasn't aware of it. It took me some time to find it back here. In Github I could find it as I installed it myself URLS for VS 2019/2022: https://marketplace.visualstudio.com/items?itemName=InfomindsAG.XSharpPowerTools https:...