>Thank you both!
>
>I'm using _INCLUDE for my clases, and now I understand it's purpose.

It's only helping you - when you create a new class (of the limited set that Sergey mentions), the content of _include is used as the default include file for that class. Which means that you don't have to open up Class/Include file in the menu and enter it yourself.

Limitations:
- works for a limited set of classes
- doesn't do anything for classes you created before you set it
- you still have to #include manually in the prg files

Watch out: if the content of your _include is not what you want, it will still be used as a default include file for any new class you create. I've had a home()+"vfp.h" (fullpathed!) in my _include without noticing it, and later had to chase it throughout my classes and replace it with my include\app.h. It can screw you royally if you don't watch.