>>>>>>>
>>>>>>>I wonder if Michel hit some walls when porting to ASP.NET from VFP. This would not be a good thing. Or he is just over his head with all the features of the VFP to be converted to .NET and it is just a matter of time when UT will have all the original features.
>>>>>>
>>>>>>Probably both. Time will most likely resolve both.
>>>>>
>>>>>Hopefully. I can only imagine that if I ever converted my app to .NET, it would be a very steep climb for me to make all features to work in .NET. Is this a good reason for me never to go there? <g>
>>>>
>>>>At the risk of starting a war (I really hope not), we are doing that now and there is no steep climb at all. Just being real...
>>>
>>>I take my heat off to you for taking the time and learning .NET. I don't know if I ever will.
>>>
>>>By the way, if you don't mind my asking, are you using ASP.NET or Win Forms for your VFP application conversion?
>>
>>Both C# winforms and ASP.NET (different modules, different puposes) , WCF on and off, and later WPF.
>
>Thank you.


Just to clarify, 'WCF on and off" does not mean 'here and there' but rather 'turned on or turned off.' Like enabled or disabled in code.