You don't even need an external RBase.dat... You can put in it your VarChar
field and Run Select in the OnConnect event of the DB.
----- Original Message -----
From: <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Friday, October 23, 2009 9:08 AM
Subject: [RBASE-L] - Re: Issues associated with packaging anddistribution
R:BASEap...
This thread made me think of something for the first time.
In the old days all our code was in a bunch of external files. That
made it hard to distribute, and people could modify or delete our
programs. But now most of us put all the code into the forms
themselves, so even without a compiler it's easy to have just
the 4 database files and an rbase.dat. So the compiler's main
function is to keep you from having to install RBase at the site,
right? And that means no "back door" way of getting to the data.
If the V9 compiler will put the forms into the compiler itself rather
than the database files, your program code is back to being safe
again. I find that a HUGE benefit ... I've never used the compiler,
but will be more likely to do so under that scenario!
Karen
>If I am not mistaken the DLL's are still required for a
>fresh installation of an eXtreme 9.0 compiled exe where
>there is not a resident copy of R:Base already installed.
>However, the ability to embed the reports and forms is
>the real beauty of this new release.
In addition, you also have the option to embed all related
External Forms File(s) (.rff) and Command Files (.rmd,.cmd,
.eep) as R:BASE resource files for your distributed compiled
application.
