>The idea is not necessarily to turn your whole app into an object. Rather, utilize an 'application' object to take care of a lot of the housekeeping type things your app has to do.
>
>Application objects are usually subclassed from the container control and have methods to take care of menu handling, form handling, read events, clear events, saving and restoring environment settings, cleanup or whatever else you deem necessary. The reason that containers make the best application objects is because container can have other object as members, such as a security object or a user object.
>You can write an entire application without using an application object, all you need is a startup program that starts the main form, or main menu in the screen and issues a READ EVENTS, but if you decide to use an application object, your main program would look something like this:
>
>RELEASE goApp
>PUBLIC goApp
>goApp = CREATEOBJECT('myappobj')
>
>gApp.Show()
>
>Then goApp's show method would fire whatever else you need to do before finally issuing a READ EVENTS. An application object usually lives through the entire program session and is called upon to do all the things I described above.
>
>While VFP's app object is not by far the perfect app object, it is stil a good jumping off place. You might want to create a dummy application with the wizard just so you can check out the various methods and properties that it uses. Hope this helps some.
>
>
>
>the application object would take care of the rest

I think I'm starting to get the picture. Thanks.