I would just want to mention that with the press released of Visual Studio 7, the management, especially our President, seems noding on VB because it can fill the gap between Delphi. Still VFP, is our primary tool that gives us so much projects. With VFP alone, the software development division personnel alone now counts at 32 from the original 6, and still growing, would you believe? We also have resellers, but we carefully gets those who believes in our product and to our software team. Good luck again!

>I don't know the market difference between East Asia and France, maybe a big difference, but here, ratio is 5:1. 5 customers are just after the app itself, while 1 customer is after what tool was used, and, oftentimes, that person belongs to IS staff that wanted PRESTIGE rather than functionality.
>
>I, myself, seems at this time confused what to recommend to our management regarding which tool to add in our arsenal: Delphi or VB??? And here is some comparison that I could speak of with 6 months (maybe not enough length of time) of doing study and research (technical/non-technical) for both products:
>
>

>VB6                            DELPHI5
>1.  Customer-based is huge     - Second to the bottom (VB,PB,ORACLE,C,VFP)
>2.  VBA support                - n/a to me so far
>3.  Not full blown OOP         - full blown OOP
>4.  much code to maintain      - lesser to maintain because of Inheritance
>5.  electronic technical
>    resources is huge          - lesser technical resources
>6.  Owner is established       - flickering company (Inprise)
>7.  books are everywhere       - not so much
>8.  speed is ok                - speed is even better especially C/S apps.
>9.  non-data centric           - data-centric
>10. no cross-platform support  - supports cross-platform (unix/linux)
>11. cheaper                    - costly
>

>
>I hate to read and see threads like this, but, I understand your sentiments Francois. Good luck to you and wish that the tool that you will be embracing will not frustrate you again. To me, I will no longer stick to one tool, "for better a Marine soldier to have two or more weapons on-hand rather than one."
>
>>Attention: Any MS marketing staff reading
>>
>>I was informed a few minutes ago that our product could not be distributed in France (our potentially biggest market) because it is fox-based.
>>
>>The product : a 3,000 hours sharp c-s repository-based generic HR development made in vfp (instead of Delphi). I pleased the marketing team.
>>
>>The market : potentially 700 c-s installations in French mid-sized industry by a significant software house. The objective : replace both an old non-scalable jet-based access development and a failed (yes it happens, folks) vb+Sql server project.
>>
>>The reason not to make the deal : rejected by the techies because fox has been used. I could not hide it in the end.
>>
>>This is, of course, not the first time. It will be the last one. I AM MORE THAN FED UP WITH MS VFP MARKETING. Why did i stay with vfp for data-centric apps (i have been leaning to Delphi for quite a few years now).
>>
>>I AM QUITTING MS-TOOLS BASED AND OTHER WIN32-ONLY DEVELOPMENT RIGHT NOW.
>>
>>Good luck to those sticking to the fox.