DBPro exes are safe, but I'm not sure about DB classic.
DBPro exes are compiled directly into machine code like the executables produced by Visual C++ etc. In this process, the control structure is greatly simplified. There are no loops or anything in machine code, it is all done with JMP (GOTO) commands for example. There are many ways of converting what is effectively the same code into machine code and although a human could possibly work out what was going on and write their own code, getting a program to automatically go through the exe and produce DBA code is (virtually) impossible. The stuff that DrunkenFingers listed above references the DBPro DLLs which are "built in" to the final exe. References to them are easy to convert into DBA code, but the important part, the control structures, variables etc. are more difficult.
DB Classic on the other hand is an interpreter, which I presume means that the original code or (more likely) a tokenised version (ie. long, wordy commands are replaced with very simple symbols) is incorporated into the exe somewhere and theoretically, it should be possible to extract it and convert it. For other languages that use interpreters, this has been done. However once the language reaches a certain level of complexity this becomes very difficult. I know that for a relatively simple language called OPL on Psion Handhelds, the reverse translator was several thousands of lines long (you could reverse translate the reverse translator
), even though the language was only half-way between BASIC and DarkBASIC.
In conclusion, I think you are pretty safe
NOBODY has a forum name as stupid as Darth Shader. I do.