How do I make dBASE compiled code secure?
I have a dBase III PLUS program which contains (and performs) confidential stock market prediction calculations. How can I best assure that in the event of my PC being stolen, the code can NEVER be read. Obviously the first step is to compile the program into 'unreadable' compiled code, but what further steps can I then take (seeing that compiled dBASE code can be decompiled) ?
Securing dBASE code
You can''t really. There are obsficators that simple change variables into simple forms like numerals - best thing to do though is to simple make sure you keep the source off your machine. Just keep the EXE... you will probably want to encrypt your dbf files as well. What version of dBASE you use is useful. If you are really concerned then you should rewrite to C++, however you probably feel you want to be able to change the code quickly. So it is a balance between security and changeablity.
Frankly what are the risks? We are the only company that decompiles dBASE code in the world. No-one has our tool and we do not sell the tool. And before that can happen the person asking has to prove that they have copyright. That normally involves that they have to match the (c) copyright holder. So one good thing is to add a dummy variable that doesn''t display - but has a legitimate operations: say copy_right="(c) XYZ enterprises 012345 678545".
This means we can contact the copyright holder. In this respect you are very safe keeping in dBASE III or IV for DOS.