Here are a few advantages:

1. ActiveX Controls are more likely to work with VB. In fact, they all do since
that is the platform on which they are tested.

2. Better support for the Windows API.

3. Ability to raise/respond/Define COM events.

4. The ability to create user-defined-types (UDT).

5. The ability to make use of enumerated types.

6. Better debugging enviornment - especially for middle-tier items

7. Lighter footprint


If you are interested in middle-tier development, especially in a web environment, VB is almost a slam dunk. From a UI standpoint, the myth exists that VB is cumbersome, you cannot build frameworks because of the lack of inheritance. VFP certainly has some advantages on the UI. When you bring up the ACtiveX Control issue, sometimes you need to VB if you want the control to work correctly. How often have you read a thread where folks are having problems getting an ActiveX Control to work correctly in VFP...

I know you don't care about the backend, but VB has some demonstrable advantages when it comes to working with SQL Server. We will leave it at that..



>John,
>
>I would like to see a list (doesn't have to be long) of what you consider to be VB's advantages over VFP. I have seen what many here consider to be VFP advantages over VB, and I have also seen your responses to those propositions.
>
>In discussing these advantages, please consider the following:
>
>- I write business apps. Inventory control, order processing, EDI, accounting etc. Pictures of our inventory items (jewelry) play a role in my apps. Also, I'm creating web-based query tools into these application.
>- I'm not concerned about the back-end for purposes of this discussion. SQL is often times the correct answer, and so may MSDE, but that does not preclude VFP as the front-end or in the middle tier.
>- I'm aware of the MS strategy for the future. This point alone may be a compelling enough reason for me to focus on VB/C++/.NET. However, for purposes of this discussion, please ignore these facts. IOW, focus on the tools as they are today.
>- I'm fairly new to VB...
>
>Thanks for the time,