>>Hi, George!
>>
>>>>However, I must admit that I'm not terribly fond of the OOP implementation, especially in VB.NET. In ways, VFP's interface to the PEM's is much cleaner and easier to use.
>>
>>Really?!? Could you provide more samples about what you don't like in .NET's OOP implementation?
>
>Actually, it's the implementation of the OOP interface more than anything else. The first on that comes to mind is as follows:
>
>Take a Winform, for example. Drop a command button on it. Double click it to bring up the code window (which, BTW, very nicely builds the code for you). You see something like

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
> ' Code here
>End Sub

Where is this code located? In the form! You can navigate or place form associated methods above or below.
>
>More than anything else, the design simply looks like you're breaking a whole bunch of encapsulation rules.
>
>In Fox, if I want to go to code associated with the button, I go to the button's property sheet and get it there. I get this very strong impression that I'm dealing with a 2.x SPR file.:-)

George;

It also reminds me of working with VB 6 (and previous versions) as well as Access. You get to see everything on "one page". Well, now we have two pages for ASP.NET - HTML and Code Behind.

The VFP IDE is so much easier to use when it comes to the property sheet.

Tom