I'm working with appBuilder/procedure editor, release 11.6 (not a Studio IDE).
Apparently, one of my colleagues has modified a window file (*.w) in Notepad++, compiled it and it was working fine. When I try to compile this file, there is also no problem.
However, when I try to open the file in appBuilder, I get error message 11678, followed by 12370, followed by 142, and those two last error messages keep on going on and on, it looks like an infinite loop.
I've been checking the files "compile.log", "listing.txt" (compilation listing) and "XRef.txt", but it seems that none of those files is modified while opening a file in the appBuilder.
The fact that those error messages appear, means that the appBuilder is doing something.
I'm not looking at the solution of this particular error (11678), I'm more interested in some logging, which might enable me to follow what the appBuilder is doing, so that I can learn what the appBuilder is doing with what part of the code, so that I can solve my issue, but it seems that currently the appBuilder is not logging anything.
Does anybody know if appBuilder logging exists and in case yes, how I can enable it?
Since the AppBuilder is just ABL code running in an AVM, you can add the following to your startup shortcut or add it to a pf file reference by your startup shortcut:
-clientlog mylogfile.log -logentrytypes 4gltrace:2
This will write all calls to mylogfile.log. If you need more logging, you can increase the logging level to 4gltrace:3 this will then also log all return values from function calls.
If you have -debugalert enabled you can also start the debugger to see what is going on.
Documentation on:
Note that you will need to use the -zn startup parameter for debugging / logging internal stuff.