>
>Hmmm. You have to wonder why MS promotes VB on the front-end and
>SQL Server on the back-end instead of VFP? Hmmm. Because they make
>more profit? :^)

MS makes no extra money off of VFP but a bunch off SQL Server.

We are in the middle of a total rewrite of two major systems. Currently they are both VFP all the way. We are keeping VFP for the front end but moving to MySQL on the back end. We have done a lot of testing and, in my strong opinion, the best way is to do simple SQL calls to MySQL and bring the data into cursors in VFP. VFP will minipulate/sort/dice and parse data far faster and easier than any SQL program. This way you have all the advantages of the rich VFP front end and, at the same time, the almost unlimited capacity of MySQL.

I do not believe in using a Web interface becuse our programs are very user intensive. We do business management systems and that means a lot of data entry and validation and a lot of grids. Maybe in 5-10 years they will have some web programming that will allow one to create the truly rich interface. But why? You can do it all now with this method.

As to how to move the data between MySQL and the VFP cursors there are a number of opinions to be found here on the UT.

For myself it depends on how much data is being moved. If I am working on one customer record and one invoice then I just use ODBC. If I am moving many thousands of records then I use LOAD DATA INFILE and SELECT ... INTO OUTFILE.
These are many, many times faster than ODBC.

John.