>>David,
>>
>>Below I have COPYed the VFP5.0 Help for the Grid container.
>>If the Help is where one is to go to "find detail info", then I hope you agree that it is quite lacking!
>>Aside from simply how it looks, how about how it reacts when the cursor is clicked in a column?... When the record-pointer is moved??? and tons of other "detail"?????
>>
>>No, the Help does not give the answers required. It is, in fact, nowhere in the docs that I have found!
>>
>>regards,
>>Jim N
>>
>>
>>-------- Start of copied Help entry for Grid
>>Grid Control
>>
>>Syntax Remarks Properties Events Methods Example See Also
>>
>>Creates a grid.
>>
>> Syntax
>>
>>Grid
>>
>> Remarks
>>
>>A grid is a container object that displays data in rows and columns, and is similar in appearance to a Browse window. A grid is also a container object that contains column objects. A column can contain a Header object and controls. Because a grid and its columns, headers, and controls each have their own set of properties, you have complete control over each element of the grid. You can create a grid interactively using the Grid Builder.
>>
>>For additional information about creating grids, see Chapter 10, “Using Controls,” in the Developer’s Guide.
>>
>>
>>--------- End of Help copy
>>
>>>> I am fairly new to VFP and I have not been able to find the detail info
>>>>for VFP's BASE CLASSES (the CONTROL CLASS for example).
>>>>I have looked in the docs and other books. Please advise.
>>>
>>>For most information, the official written documentation for VFP is not usable. Most of what you'll need is in the main Help file.
>>>
>>>Don't forget that it is better programming practice to subclass your own base classes, rather than use the VFP base classes directly.
>
>Why is it better to subclass your own base classes, rather than use the VFP base classes directly?

Actually Rob, one of your earlier posts may have answered that. One of the things that's great about OOP is inheritance. But if you can't modify the parent, then you can only inherit the base fuctionality, which isn't as robust. As a matter of practice, before embarking on any application, I create a base library (or use one I've previously created) and base nearly all my objects on those base classes. Therefore, I ALWAYS have someplace to put shared code. Creating you're own set of base classes simply give you an additional level of global control over your app.

HTH