>> Of course. The look of the class is up to you, even after you subclass it.
>
>> There are classes in the FoxPro Foundation Classes (FFC), but I don't think many would use them for a significant application.
>
>Hi Mike,
>
>I saw this _table.vcx (FFC) with nav4buttons as a container. Why can I not use this? Sorry for asking. I am very new at VFP programming. I just started last October 2006 learning this on my own. My work wanted me to learn it and take over this application and even convert it to a new platform (VFP 9.0).

You can use the FFC classes, but... "learn it" and "take over this app" is not necessarily referring to the same thing. FFC classes are an interesting read, and the code in there is a good place to learn a few things - but then it's not what you'd want to use in real life. You may take a few ideas from there, and find some useful bits of code. Using FFC (specially the forms and buttons) in a real app is pretty much like creating a website with FrontPage and keeping all the default styles and structure, just replacing your text and possibly heaving a few pages titled "Caption goes here".

About once every VFP version I cook up a form for my own use, using FFC, and get to hate it within a week. Why? The Edit button. The idea that whatever I'm doing, I have to tell my form first, otherwise it's readonly. Want a new record? Click new. Want to edit a record? Find it, then click edit. Want to move to another record? You get the "save?" reminder. It's somehow unwieldy.

Also, a lot of FFC code is just heavy and unnecessary for real time. SetObjRef.prg and anything related to that - you can do that simpler, or do without it. Most of it was written for VFP3.0 ten+ years ago, and didn't change much. VFP has all those years of experience now, and we can do all that better and much more elegant. FFC has a few neat tricks under its hood, and you can refer to it (or the stuff in Solutions directory) to see how things can be done, but you won't learn style from there.