>>>>>Hi Craig...
>>>>>
>>>>>I made an EXE and when I invoke it, it has the _screen behind it.
>>>>>Is that suppose to be there? How do I maximize it?
>>>>>I can control the menu displayed and the tilte on the _screen.
>>>>
>>>>have you tried
>>>>
>>>>_screen.maximize = .t. ?
>>>>
>>>>it may be _screen.windowstate = 2 (i'm forever getting vb and vfp mixed up in this area)
>>>
>>>Do I have to code all the settings I need for the _SCREEN stuff?
>>>Is there a PROPERTY WINDOW?
>>
>>There is no property window for the _SCREEN. There are documented in the help file.
>>
>>Craig
>
>I found it in the help file and thanks to you and others, I will put
>code for _SCREEN in my oApp object at startup. I am sounding more OOP these days...
>
>also.. check this out from a "use to be" clipper programmer...
>
>How I did it...
>
>RE: Visual FoxPro 5.0
>
>I first started out by trying to make anything work...
>
>After I got the "hang of things"...
>
>I started writing CLASSES and then SUBCLASSING... then
>
>I started writing functions, now called METHODS, and using PROPERTIES (was called memory variables)...
>
>Now, I am writing my methods for my objects, smaller and more generic...
>
>Over the hump...
>
>Rob
>
>thanks Craig...


No problem.....one thing as a former Clipper programmer..you're probably familiar with dLesko's tool kit for Clipper Funcky is the name of it). Anyway, when Clipper 5.0 was announced, Dirk Lesko said that OOP is doing everything backards from a procedural way. In procedual codnig, you throw a function at the data. In OOP, you throw data at a function. Then he added that it's just the same way of doing things...but with different names for them (variables...properties, procedures/functions....methods). OK, so it sounds like Dirk contradicted himself, and at the time I was confused...but not anymore.

Craig