>>>>>If you have a separate data layer then you will only adjust that portion if you want to because I don't think succeeding versions will totally replace the entire thing. There will always be backward compatibility I think. LINQ maybe just an option to handle data although I don't have any idea as to how it works now. What I really want with .NET is that you can create an application with a presentation layer that is awesome. You have so many options which is not so in VFP. We are stucked to where it is now (at least for Windows Forms).
>>>>
>>>>I'm not sure whether you've seen what you can do with GDI+ in VFP9, but that is good enough for me. The rest really depends on the creativity of the developer.
>>>
>>>How about the limited number of UI controls in VFP? Specially the very limited GRID...
>>
>>I've managed to do with the grid for years. Not so much a problem for me. As for the other controls. Yep you're right .NET allows very good controls, however with the help of some activeX controls I can live with the current state and can't see that as being a reason to make the jump. After all we are not in a GUI beaty contest.
>
>Impressive GUIs matters especially now that users wants user friendly applications. Ofcourse, GUI is not the primary reason of jumping into .NET but it is a big factor if we are to consider user friendliness of the application. Maybe, the reason why you are not sold yet to .NET is that you are at your comfort zone or maybe you don't need .NET yet. But come to think of it, if you only adopt .NET because you've seen it's already widely accepted, then will be in trouble. Sooner you will realize that you are chasing something that is hard to chase.

Impressive GUIs <> Effective GUIs. I can build effective GUIs without a problem in VFP. I can build pretty GUIs as well in VFP. If you're an artist and want to make revolutionary eyecatching GUIs you're better off with .NET. But those GUIs tend to be less effective as the prettyness distract from the functionality.

Walter,