>Also, I have read that the more subclassed controls that one uses, the longer
>forms take to instantiate.

I've seen benchmarks with 10 levels of inheritance run at essentially the same
speed as baseclasses.

>In my company, the owners don't want to hear that we need to replace all our
>current workstations (primarily P75's with 16 megs RAM) with P200's with at
>least 64 megs of RAM to get an app that performs at a decent level.

I used to do VFP5 development work on a P75 with 32M, and it was quite fast
enough for most purposes....

>I know my users do not like to watch pageframes refresh from one to the
>other...

ThisForm.LockScreen = .T., etc.

>I also must vent about VFP's DBC. Why would I spend hours setting up all my
>tables with proper field mappings to MY classes only to have the WIZARDS
>totally disregard them? I would not call that RAD.

I stopped using the wizards within about 5 minutes of my first try. If you
checked the documentation, you would find that the form wizards are designed to
use their own classes. If you want to use the wizards with your own classes,
create your own form template. Instructions are in the Online Documentation.

>In addition, why is the path to MY class library hard coded into the DBC?

Ummm... because you put it there? Try only typing in the class name and
setting the PATH appropriately so the DBC can find it.

>I see why most other developers do not respect VFP as a development tool,
>certainly not as a product for building robust applications.

Most other developers THAT YOU'VE ASKED. If you asked people who had spent
the time figuring out the answers to your questions, you would not be so
frustrated at VFP's quirks.

>In fact, most professionals in Northeast Florida ask, "Why would you want to
>use FoxPro?" I look forward to a response from the hard core VFP developers
>out there...

Because it works. In my previous position, I had set up a framework that
allowed me and the other developers in the office to toss together applications in a very short time. It was also robust enough to handle almost
anything we wanted to do, including parent-to-two-childen relationships,
parent-child-grandchild relationships...