Keeping true to the MS Hides VFP campaign, after installing Office 2003 and Visio 2003 last night I was not surprised to see that, once again, MS did not reinstate the native Visio VFP Driver (Ixvfp..pdl or whatever) for database modeling. Yes, the "generic" VFP ODBC and VFP OLEDB drivers work for reverse engineering a VFP DB and free tables with Visio, but the Visio DML generators do not forward engineer VFP usable SQL to use for creating or altering the tables when the model is changed.

Sure, more and more VFP apps are written other backend DBs, but why should we have to go out and buy a third-party modeling software like ERWin, Embarcadaro, etc. when MS has a product that is supposedly being geared to compete with the other products and included in the cost of the MSDN Universal price...

Yes I've e-mailed MS Visio support a few times (and Ken too) about the removal of VFP support from Visio and it'd be nice if more VFP developers did the same. The sad thing is that Visio used to have a native VFP driver for modeling, and within two releases of buying the product from the original company, MS removed it.


Just venting,

- Brian