YOU GOT ME ALL WRONG ON RIO!

Look - there was a reason for that challenge - a lot of VFP software does little jobs - little value added kind of software - rudimentary inventory sales and purchases, baby payrolls, receipe books, datablending utilites and OLE interface stuff. Little evalware or shareware stuff that those low to middle tiered-end users. There is a great big market that does not require an enterprise solution (though vfp - if the programmers are dedicated, can build great enterprize solutions).

Something they can download and install quick. On the RIO challenge I would not have cared if you used a text file - just to avoid the pain of ADO and the complications of ODBC. But that was a basic framework using low-level xbase and activex.

Most of us that book full project work have to have some kind of framework. I wouldn't think any other xbase(DBF)/activeX toolkit would be much different. There just are "so" many less than obvious ways to solve the problem in that context!

BUT YOU HAVE ME ALL WRONG! I wanted to see it work. I really did - even if you had to fudge some of the features - I was hot to see it. I was not setting you up - I believed - that since you guys had hooked up with EPS - and the claim was VFP to NET conversion - that some kind of faxcimile would be built. You'll have to admit, RIO is about as small of a project as there can be!

At least I did not remind you that you failed to convert a little VFP 1 former to DOT NYET!:)
>
>Terry, for about the 10th (and final) time - I refused to take you up on your "challenge."
>
>You are so programatically anti-.NET that nothing would be achieved. I don't work for free. I've got enough on my plate, all of it more important than that.
>
>Here's a better idea, since you constantly mention "failing the challenge" - why don't YOU take some time and go through a couple of iterations of a .NET version?
>
>Kevin