Hi, John-
I can't speak for Justok, but one of his suggestions is the same as others (including me < s >) have made to you. If you compile your forms, reports, and classlibs into your EXE you can then use REFOX to encrypt (and protect) your code. REFOX has a setting that will not allow REFOX to be used to decrypt your EXE without a password. I don't know the details of how, my partner handles that aspect of our project, but it does address your concern.

The problem with this is that if you need to make changes to a library, form, or report, you must redistribute the EXE. It's up to you what balance you need.

As for Justok's comment about leaving reports separate--I've read threads here by people who do include FRX in the EXE, but copy it out to a report on disk that users can access to change and customize. This sounds like an excellent idea to me, because it means the original is always safe from being lost, but gives the user's flexibility.

Good luck.

> Now, I know how to manage my copies of source code. However, I still don't see the advantages from method and property protected or hidden. Can you give a a situation or senaria of it?