>>It probably more like VB - the data would need to be shunted to an intermediate ADO object just to get a recursive. Too many intermediate data sets mean the hour glass would be fairly obvious. I saw an almost completed VB.NET (it's been almost completed for a couple of years) project and there was a lot of hour glass.
>
>Terry,
>
>I enjoy your creative posts so don't take this too personally, but that didn't feel like a complete answer The only thing not related to the data engine you mentioned was the size of the runtime. Nowadays - unless you are talking about very small markets - that isn't an issue. I read the back-and-forth on the challenge and it wasn't done because they chose not to do it, not because it couldn't be done. I thought that it would have been fair for the challenge to have been accepted, but regardless the stated reasons for it not being done is different than what you mentioned. Is there anything of substance beyond the data-centric aspect of Foxpro that cannot be done well in .NET?

I don't know - I have not seen one .NET GUI - So I really don't know - no idea - I am a lumbering ignoramus on that subeject - I develop - I don't write white papers or tour the DEVCON circut. Just a simple bread and butter programmer.

I don't know. When MS stock gets back to 100$/SHare, or when I go to a Best Buy or Circut City and see Turbo Tax written in .NET - I will tell you:-). I have heard that costs to implement and maintain are a factor people do not want to talk about. My market is not IT management. I don't think the paradignm is as broad - but thats just a suspicion:-). How about speed - does .NET make ADO faster? ADO is just as sluggish with .NET as I suspect it is with VB (or VFP, even!)

I think .NET is like a real expensive and big version of Access - one modal form for one list - but I don't know - just impressions! I know with VFP I can populate one form with as much data (from many sources) as the real estate will handle (without subforms or any of that restrictive paradigm stuff). I know there are discrete properties and methods on the control palette that I have not seen in other MS tools. If microsoft wants the VFP community to help it sell .NET - rather than allowing insiders and "speakers" and "writers" to bash it - they should give "developers" an option to to sell VFP.NET to endusers. Give us all the legacy stuff we are used too - and add all that stuff that they need to sell there other stuff that will help MS with needed recurring sales.

I have not even seen a .NET interface - well once - at my SIG - I think I saw one - but it looked like an old-school consultant's interface. I think .NET is great for the DEVCON presenter market and large consultant firms. ADO is awkward (compared to a cursor). It seems just a new face to wrap around the same old Mr. ADO - But I don't know - I barely use 10-20% of the VFP paradigm - and even with that - I am writing 7 days a week.