I always advise, that at the beginning of testing RadCORE you should use the ORIGINAL version, ie, do not start changing things before learning the basics.

If you are going to test any version of RadCORE with database, try to install exactly the version of FIREBIRD indicated.


"Learn to walk, then you can run"


When you are mastering the principles of use, you can migrate your database, report generator etc.


Another very important point: We are all programmers !


Even if RadCORE is new to you, it is a DELPHI/UNIGUI application, so you can always DEBUG and locate the points where errors occur WITHIN THE RADCORE PROJECT and report so we can fix as soon as possible, but remember:


- If you have created a specific version of RadCORE and changed the "default flow", maybe I will not be able to help.



RadCORE is UNIGUI ! 

And in unigui we have the folder "LOGS" that bring us information about the flow of application execution that can guide on the problems that are occurring.

Besides that, RadCORE brings a function: rc_ConsoleLog that uses the "execution console inside the browser". With this we can create points inside the application to present details of the execution and thus be able to locate errors that we can't in DELPHI's DEBUG.











*** This topic, as well as all others, may be updated.


Created with the Personal Edition of HelpNDoc: Easily create EPub books