Hi Evan,

>Could you defend the statement...

>VB is a BETTER C/S front end - OOP aside.

>Please list a series of facts that backs up this statement (not an analogy).

Sure....

1. VB support for ActiveX controls is better than VFP. MapX - the folks at
MapInfo come to mind here. I could not get that control to work correctly
in VFP. So, I had to resort to using a VB front end. My opiniion is that
the fault in all of this is the vendor - not testing their product in
VFP. But, from a business standpoint - they probably see 1/10th or 1
percent of thier customer base doing this. They probably say - why bother.

2. VB supports ActiveX Data Binding with ADO. This is imporant. I mean -
really important... ADO and OLE/DBis probably the most imporant technology
to come out of Micrsoft since Windows and ODBC. Microsoft wants to be a data
company. The new OLAP tool - Plato - is ADO based. All of Microsoft's data
warehousing efforts are gearedtoward ADO and VB. While much of this is in
the future - the Data Binding with ActiveX Controls exists today.

3. VB is 3x-4x lighter than VFP. It takes about a mb - maybe a bit more - to
load VB. Yes, VFP is lighter weight than it used to be. But compared to
VB - it is a pig of a front-end. It takes at least 4 megs to load VFP.

4. VB has a true compiler. Once again, making a lighter weight front end
lighter and faster.


Hows that???