>>In general, you could create an OBJECT base on CLASS. And so, if you want your entire application be created as one object, you might as well create your application as a class first, but I don't think this is a good approach.
>
>I got the feeling that there's already an application class. He didn't say anything about creating a class; just an object.
>
>I looked through the code generated by the wizard and found this:
>
>goApp=CREATEOBJECT("cApplication")
>
>
>That seems to be where it's doing it. But how does it know what "cApplication" is. I don't see it defined anywhere.
>
>Thanks,

Class can be defined Programmatically or Visually.

Visual FoxPro searches for the class or OLE object in the following order:

Reference portion of CREATEOBJECT() on VFP help system
1. Visual FoxPro base classes.
2. User-defined class definitions in memory in the order they were loaded.
3. Classes in the current program.
4. Classes in .VCX class libraries opened with SET CLASSLIB.
5. Classes in procedure files opened with SET PROCEDURE.
6. Classes in the Visual FoxPro program execution chain.
7. The OLE Registry.