>>>>>>What is the reason for the "Application Object" or
>>>>>>"Application Class"?
>>>>>>
>>>>>>Rob
>>>>>
>>>>>It replaces...and enhances the _SCREEN object. In a remote automation server, you don't have a screen, so you use the application object.
>>>>>
>>>>>Craig
>>>>
>>>>Thanks Craig for your answer...
>>>>
>>>>I guess that means, you do not have to use the Application Object in your programs if you do not want too...?
>>>
>>>
>>>Robert,
>>>
>>>Sorry to take so long to get back to you. I was out of town last week.
>>>
>>>The _VFP application object is always present in a VFP 5.0 application. You can't get rid of it. In addition, most frameworks create what they call an applicaiton object from their own application class. This handles things that the framework needs and is different than and not related to the _VFP object. I hope this doesn't sound too confusing.
>>>
>>>Now, to answer you question...no, you don't need to create your own application object/class, but it is the OOP way of doing things. It will contain properties that would have been PUBLIC variables in previous versions of Fox.
>>>
>>>Craig
>>
>>
>>Thanks Craig for your answer... it helps alot...
>>
>>One more question if you don't mind?
>>How do you get rid of the caption area in a form window?
>>I am trying to have some basic information on a form and
>>using a "more information" command button, I would like to call another
>>form that shows more information. Everything works but the caption
>>border area looks like another form and not a continuation of the same
>>form.
>>
>>Rob
>
>
>Rather than make it another form, put all the fields on the original form, then in the Form Init, make the form shorter (change the Height property) to hide the fields. When the user click on the More button, again change the height of the form to display the other fields.
>
>Craig

Craig...that was a great answer...
I am a clipper programmer moving to visual fxpro.
Thanks for your help...