Issues associated with packaging and distribution R:BASE applications
We have compiled the application we have developed (BMS Interior Design Pro)
using R:BASAE compiler:
after that was done the application becomes
our_db.RX1
our_db.RX2
our_db.RX3
our_db.RX4
our_codelocked_procedures.dat
program.exe
<couple of required DLLS>
Looking at that I see the whole point of the
compiler is in: allowing us ship our application without requiring
our customers to purchase R:BASE.
But this is only minor part of the story why we needed compiler
in the first place, we also want to prevent our customers from being
able to open up and modify our forms using purchased or evaluation version
of R:BASE. I do not see that compiler accomplishes that.
Another thing: copy protecion we need to be able to lock to single PC
our application, with all the software piracy going on and torrents and things
like that without good copy protection it becomes difficult to make money
selling software.
Whats is the R:BASE recommended solution for copy protection of shipped R:BASE
APPLICATIONS?
Boris Tkachenko
Director of Software Development
BoMar Software Inc.
Lenexa, KS, 913 687 2263
