This is repeated from my reply to the VFP vs VB thread of Aug 14. Click on the calendar icon in the upper-left frame, set the filter to the VFP In General category, and click on the Aug 14 date. Read the entire thread on VFP vs VB.

The big advantage is the VFP DBC. The choice to mix and match local and remote views, local tables, different backends, free tables, updatable views, SQL passthru are readily and easily available to manage data. How easy and efficiently can you do this in VB?

In one of my apps, I have several connections, each to different backends -- Oracle database in North Carolina [the app runs in the Dallas office], an MS Access MDB, and a local Oracle database. Seemless and invisible to the users as well as fast. I really enjoyed developing this because of the excitement of learning I could get data from anywhere and the implications of this with respect to VFP web development.

Challenge your VB proponents to match this ability just as easily in VB as you can in VFP. Tell them if they can do it, you will agree to switch to VB. Give them a reasonable time limit, say a week. This time next week, you will have a bunch of VFP believers.