>Hi,
> 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?
>
>
>Thank you

---

Sorry, John. Since my project is for internal use, I don't need to hide/protect my code. Of cos, most users don't know foxpro and have NO foxpro program installed and thus they fail to edit my source!

What's more, as I recently mention, I Don't disturb any VCX files to application path and most form objects are instances only!
Even I disturb the form out, most code will be protected!

If you really want to hide ALL code, try to make Formset and Form class,
and the scx form is an instance of class. There will be no code in SCX even in your VFP program!

Good Use on Inheriance will make good protection on coding unless ppl get your VCX files...

---

Actually, when I study C++ in college, protected and hidden are under OOP concept. Of cos, I am NOT an OOP expertise, maybe I misunderstand some.

OOP try to "View" all things as Object.
Object allow to hide some information from other, so that it can get save on others unauthorise editing. For this reason, there will be a hidden property to do. (e.g. No one can use your $$$)

For Protected, it will work for inheriance. What it likes!?
(e.g. Your son can use your $$$) Only inheriance objects can use the protected elements, for outside objects, none can use it!

---

Now, actually is quite meaningless, unless you build an application with many many ppl, and YOU don't want ppl to read your source-code.
You make your own VCX and set all properties to PROTECTED.
then you ask your pn to use outer reference to your VCX file and do additional coding. For outside ppl, no one can get your code but your pn can call them to use..

Actually is quite hard to understand. ~_~