Zerlauth,
Yes, most likely these are old 16 bit Wise installers.
Do you need ReportPro for VO or for X#?
And for which version of VO?
Robert
Search found 2512 matches
- Fri Apr 17, 2026 2:57 pm
- Forum: 3rd party products
- Topic: ReportPro Installation Problem
- Replies: 5
- Views: 462
- Fri Apr 17, 2026 2:38 pm
- Forum: 3rd party products
- Topic: ReportPro Installation Problem
- Replies: 5
- Views: 462
Re: ReportPro Installation Problem
Zerlauth,
Where did you get the ReportPro 2 installer?
Robert
Where did you get the ReportPro 2 installer?
Robert
- Mon Mar 30, 2026 10:37 am
- Forum: Chit-Chat
- Topic: epDBU DBF Administration tool
- Replies: 11
- Views: 1178
Re: epDBU DBF Administration tool
Dick,
This is a compile time code block.
Macros are strings that are converted into a codeblock at runtime
If you change the declaration to
then it works
Robert
Code: Select all
lBlok1 := {||AScan(aRel,oDBDCSUb:FIELDGET(#relatie))<>0}
Macros are strings that are converted into a codeblock at runtime
If you change the declaration to
Code: Select all
LOCAL bFor, bWhile AS CODEBLOCK
Robert
- Sat Mar 28, 2026 8:23 am
- Forum: Chit-Chat
- Topic: epDBU DBF Administration tool
- Replies: 11
- Views: 1178
Re: epDBU DBF Administration tool
Dick,
With regard to the error with the codeblock:
How did you declare bFor and bWhile?
There is a different in X# (and VO) between CodeBlock and _Codeblock. The first is for compile time codeblocks and the second for macro compiled code blocks.
Robert
With regard to the error with the codeblock:
How did you declare bFor and bWhile?
There is a different in X# (and VO) between CodeBlock and _Codeblock. The first is for compile time codeblocks and the second for macro compiled code blocks.
Robert
- Mon Mar 23, 2026 7:23 pm
- Forum: Product
- Topic: Documentation issues
- Replies: 16
- Views: 1628
Re: Documentation issues
Guys,
This is indeed an internal function. I will remove the docs from the help file for the next build
Robert
This is indeed an internal function. I will remove the docs from the help file for the next build
Robert
- Tue Mar 17, 2026 2:18 pm
- Forum: Product
- Topic: Documentation issues
- Replies: 16
- Views: 1628
Re: Documentation issues
Kees,
The compiler knows that it is an int.
What you see in this tooltip is coming from the XSharp.RT.Xml file.
That file is generated from documentation comments, and is apparently not correct.
And w.r.t. that website: that website is maintained by Wolfgang. We have no control over that
Robert
The compiler knows that it is an int.
What you see in this tooltip is coming from the XSharp.RT.Xml file.
That file is generated from documentation comments, and is apparently not correct.
And w.r.t. that website: that website is maintained by Wolfgang. We have no control over that
Robert
- Tue Mar 17, 2026 10:34 am
- Forum: Product
- Topic: Documentation issues
- Replies: 16
- Views: 1628
Re: Documentation issues
Kees,
AUTO means that the compiler will AUTOmatically create a backing field for the property and the matching Getter and Setter.
I will check the docs and add a description.
Robert
AUTO means that the compiler will AUTOmatically create a backing field for the property and the matching Getter and Setter.
I will check the docs and add a description.
Robert
- Sun Feb 08, 2026 1:22 pm
- Forum: Product
- Topic: Use AI to explore XSharp (across the entire GitHub repository)
- Replies: 5
- Views: 1057
Re: Use AI to explore XSharp (across the entire GitHub repository)
Xinjie,
This is fascinating. I find the descriptions overall very good. Is this based on the source code only, or does this include information from others sources as well?
Robert
This is fascinating. I find the descriptions overall very good. Is this based on the source code only, or does this include information from others sources as well?
Robert
- Tue Jan 20, 2026 5:19 pm
- Forum: Product
- Topic: Event handler changes not in GIT
- Replies: 10
- Views: 1935
Re: Event handler changes not in GIT
Dick,
Git does not "know" anything about event handlers or any kind of code.
It works at the file level and compares changes between the original and the changed code.
When your event handlers are no longer there, then there was an error when merging the changed code and the original code.
Robert
Git does not "know" anything about event handlers or any kind of code.
It works at the file level and compares changes between the original and the changed code.
When your event handlers are no longer there, then there was an error when merging the changed code and the original code.
Robert
- Sun Jan 18, 2026 10:29 pm
- Forum: Product
- Topic: Macro code in preprocessor?
- Replies: 1
- Views: 585
Re: Macro code in preprocessor?
Isaac,
If you are building with VS/MdBuild then you can create a build task that generates a file with this info and add that file as Compile Item to the build script.
Robert
If you are building with VS/MdBuild then you can create a build task that generates a file with this info and add that file as Compile Item to the build script.
Robert

