&
&
This is part of RoAccess and Stand Alone RoLoader.
You can enter 1 or more RPL statements. They will be run in a WEB environment. This simulates exactly how these statements will work in actual production circumstances. This allows you to test certain functionalities without having to write a set of small WEB programs. Complex sets of RPL can be given. Since RPL commands are not documented very well, this is an ideal way to determine exactly how the various RPL commands really do work in the shortest possible amount of time.
If you are going to ultimately use conditional and flow control statements like IF...ELSE, WHILE, REPEAT, etc., you can click the "Run Pre-Compiler First" checkbox. That way after you code works, you can copy and paste it into a custom application if you wish.
You can start with simple statements, then add more statements, each time merely clicking the "Run Query" button to see what your new statement did.
This is a typical screen snapshot:
 |
 |
When you click "Run Query" the results are displayed in another window. You can place these two windows side-by-side for rapid testing, so as you enter a new or changed query, it immediately displays in the other window.
 |
 |
 |
 |
If you click the "Run Pre-Compiler First", your RPL statements will be sent through the Rochade RPL pre-compiler first. Otherwise, the pre-compiler will not be invoked at all. This allows you to run code simulating a direct and a pre-compiled WEB environment.
You can use IF/ELSE and other control instructions, because the sequence of Instructions are compiled first. Use the BEGIN-DATA and END-DATA for places where you would usually use
#$APPEND instructions or data .
If you are utilizing RoDbServers, constant connect servers, then by default, any code run in the Command Interpreter window will run outside the RoDbServers so any configuration path changes will not overwrite those currently in effect in the current RoDbServer. However, if you want to run inside the RoDbServer, you need a line like:
; USE_ROA_SERVERS
This instructs RoAccess to run your code in your RoDbServer, if you are using a constant connect RoDbServer.. This is useful in testing under the RoDbServer environment and outside of it.
Do not use the "$XXX" form of Rochade commands. Instead, use "#$XXX". The Rochade documentation says this is acceptable to drop the leading # character, but there are cases that your code will not work. The Rochade RPL interpreter has what we consider a bug. $SDC will work if you execute the instruction directly but not if you execute it in a work area. If you put $SDC or any $XXX (where XXX is any legal RPL instruction) in a work area, it will not work if you execute those instructions from that work area. Example:
#$MAKEG WA_SRC #$REDLN WA_SRC #$DEL 1 $ #$APPEND $SDC APPLICATION ACT 1 . #$QUIT #$DO WA_SRC
does not execute correctly. The $SDC instruction is merely placed in a work area and the work area is executed. Rochade interprets the $SDC as data not an RPL instruction. If you put "#$SDC ..." in the work area, then the work area will execute correctly.
If you put $XXX instructions and chose the Pre-Compiler, it puts the compiled output into a work area, and then executes that work area. Since a work area is being executed, any instructions not starting with #$ will be treated as data, not instructions.
So, ALWAYS use the #$XXX syntax for RPL commands, NOT the $XXX form.