I thought if you had an Owner password the RB* files are safe and if the Forms are compressed the Custom Form Actions and EEPs are safe too??? or am I wrong.
I am using the Compiler in 7.6 to Compile the RBA file which mostly has menus. Updating my app and adding new Forms / Reports is easy. If you use V9 Compiler and put those things into the Exe will that make it harder to Add new Forms to your app? Would you have to Re Compile the EXE again to include the new Form? Thanks for any info Marc From: [email protected] Sent: Friday, October 23, 2009 8:08 AM To: RBASE-L Mailing List 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.
