>Why are the FoxPro forms (VFP 5.0a) still the slowest that I have seen in any Microsoft or Borland development tool? VC++ 5.0 and VB 5.0 as well as Delphi 3.0 (all products that I have evaluated) have forms which respond and refresh at more than exceptable speed, while my users complain about how slow forms are in my VFP 5.0 app. We are in the midst of slowly converting a FoxPro 2.6 (DOS) system to a Windows platform...

Well I have also seen places where Delphi was more slower than VFP. It depends on what you want to do with a programming tool. Refreshing unnecessary is a performance penalty in every language. If you think form refreshing is so slow in VFP, have you tried VB or Delphi with million records.

>
>Also, I have read that the more subclassed controls that one uses, the longer forms take to instantiate. What's the purpose of making VFP truly object-oriented if an already slow interface takes further performance hits? 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 know my users do not like to watch pageframes refresh from one to the other...

You needn't upgrade to P200. But sure upgrade to more RAM. RAM has more impact on performance than CPU when it's Win. On a P75 with 16 Mb RAM, even Win95 itself is rather slow.

>
>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. In addition, why is the path to MY class library hard coded into the DBC? What's the point of having an IDE that allows me to specify additional classes and their locations (as well as provide further search paths) to only have the DBC tell me that it can not locate the class library and that it will remove the association? After all, I may want to work on the project at home where I do not have the same drive mappings as at the office!

For hardcoding simply put your dbc and tables into same dir. So you could move them anywhere. DBC's are not just for mapping classes and if you only use them for that you better use free tables like in old FP. You could rapidly develop applications in VFP but then I don't know if an application would be called a RAD only if it did all via wizards. DBC and IDE are not the same thing.

>
>I see why most other developers do not respect VFP as a development tool, certainly not as a product for building robust applications. 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...

Why would you want to use FoxPro ?
I wonder how someone asking this question could be a professional. If you call someone "programming for money" is a professional then it's OK. Well show me a better one (cost/performance lower) and I'll use it. For details see the articles here in KB section and on MS site.
As to your title assume "Only data retrieval is quick". Since there is no application that could live without data retrieval, it's the major factor why I use FP.
Regards
Cetin

>
>Regards,
>J. Mendenhall
>Manager, Information Systems
>Reinsurance Management, Inc.