There are a couple of things that can easily be done. 1. Set trace off on all forms, reports and labels. 2. Put an owner id and password into the database and use that id to internally log into the application on the first connect. Encrypt all files outside the database. Password protect any external forms. 3. Click on the link below to see the enhancements for R:COMPILER 9.0. and evaluate if this may be a path to persue.
http://rbasedevcon.blogspot.com/2009/10/product-showcase-and-highlights.html Regards, Ken ----- Original Message ----- From: [email protected] Date: Monday, October 19, 2009 10:42 pm Subject: [RBASE-L] - Software Security To: [email protected] (RBASE-L Mailing List) > > We have just completed our first app. > I have to add some data and then we can compile our first demo > version 1.0 for evaluation. > Our only security is the complier right now.( 30 day demo ) > What is available from Rbase and what are other people using for > a distributed application? > http://bmsinterior.design.officelive.com/default.aspx --this is > the most current site. > I have new forms and the changes will be made this week-end. > Sorry to miss the conference, but next year I should have some > stories to shares. > Thank you, Boyd > > >
