Hank,

I’m happy to hear about your success with MM.Net. I hope I will soon become an evangelist.

Remember back then, every since the dbase2 days, we have heard from the language vendors that they were coming out with products to make your life easier, to simplify things. A few years ago I heard that with all the new development tools on the horizon the need for programmers would begin to decline. However, as long as vendors like Microsoft continue to come up with products like .Net our jobs are very secure. As one thing gets simple, there are 10 new features that only add to the complexity. I love the challenge but I get a little un-nerved when learning new stuff makes me feel like I’m moving backward. There was a time I thought it was a challenge to write a dbaseII app. To get it to do much was a real trick but because of the limitations it was rather simplistic. Now .Net has everything we ever wanted in a development tool but will never live long enough to master. There was a time when I felt like I was a master at the tools I used but with the pace and complexity of progress I must get used to the idea that the best I can do is master little niches of my trade. If the trend in development tools continues, can you imagine what future .Nets would look like?


Best Regards,

Terry Carroll



>Hi Terri,
>
>that's why I've been waiting. <s> We currently have the ability to access multiple data stores transparently and simultaneously, and easily, using a combination of tools. And we can do web services that bring all the data rules with them, and the app object can run in asp.net or as a separate REST web service. So the thought of switching ...
>
>Like you, been at this for a while (dbMan in 86 on an Atari ST 520 modded to 1024), have seen the tremendous improvements in language and capabilities. I have hope for the future. <s>
>
>Hank
>
>>Hi Hank,
>>
>>Thanks very much for taking the time to respond. I have been a dbase programmer since 1989 and FoxPro since vs 2.0 in 1991. Over the year I have learned to love frameworks especially those developed after 1994 using OOP. I purchased Kevin’s book .Net for Visual FP Developers at his booth at a VFP Devcon before he released his .Net framework. I got so psyched up about his .Net framework that when I finally had the opportunity to use it, I was disappointed because it wasn’t comparable to what I was accustom to seeing in VFP frameworks. It is finally sinking in that Kevin is developing in .Net and not VFP, which I suppose makes the task much harder.
>>
>>The best thing that could happen to .Net is to get as much VFP influence as possible and I’m sure Ken Levy will work hard to get our 2 cents worth presented to the .Net development team.
>>
>>If the VFP community sticks together the way we have in the past we will be ahead of the game, as we move to .Net.
>>
>>Thanks again for your encouragement,
>>
>>Terry Carroll
>>
>>
>>