Hi Doug,

>The only hard part is getting used to using "This" instead of "Me", so the >VFP team adds a feature to Beautify to do that automatically.

Actually we found a way to get around this problem too. In the Load event of the form add the following lines. This allows us to use thisform.txtMyTextBox instead of Me.txtMyTextBox. :)

    Dim thisform As frmMyForm   'Name of the form
    Protected Overrides Sub OnLoad(ByVal e As System.EventArgs)
        thisform = Me
    End Sub

Kamal

>I've uncovered a new Microsoft conspiracy: migrate all VB developers to VFP.
>
>Several years ago, the honchos at MS decided to kill VB and move everyone to VFP. However, they realized they couldn't do it overnight -- there'd be too much uproar. So, here's how it's playing out:
>
>- MS releases Visual Studio.NET and kills VB, forcing millions of VB developers to migrate to VB.NET. As part of the migration, they learn what OOP is really about.
>
>- Under the guise of a great library of utility functions that make developers more productive, the recently released Visual FoxPro Toolkit for .NET gets VB.NET developers used to using VFP syntax, such as ASCAN() and GETFILE(), in their applications.
>
>- In a year or two, MS kills VB.NET, forcing millions of VB.NET developers to migrate to VFP. However, this isn't a painful migration, since they already know OOP and VFP syntax. The only hard part is getting used to using "This" instead of "Me", so the VFP team adds a feature to Beautify to do that automatically.
>
>In the words of Whil Hentzen, I swear I'm not making this up -- it was leaked to me by an MS insider who only identified himself as Sore Throat.
>
>Doug