>The guidelines actually say that you SHOULDN'T use this or me, but I find it makes things much clearer to read - it gives the scoping and it also provides the intellisense more easily when actually typing code.

Really? That's surprising that guidelines would advocate not using them ... that is one of my pet peeves when programmers DON'T use "this" (or "me"). That's something I try to stress to the other developers I work with ... to always use "this" ... I get very irritated with them if they don't. <g>

>To some degree guidelines are just that - guidelines. But I've found that the .NET guidelines actually make good sense.

Except for the above. <g>

~~Bonnie




>>Totally agree with you Rick you any could see my 1st .net Project I had loSqlCmd and loSqlConnection all orver the place now I defile as sqlCmd and sqlConnection when local vars e.g. dim statments and SqlCmd as SqlConnection when properties of an object, also I always use Me. is not necessary but I like to use it since right away as I look into the code I see that is a property from the object and not a parameter or something.
>
>
>Yeah I do the same, although I tend to get sloppy at times sometimes using this. and sometimes not <s>... The guidelines actually say that you SHOULDN'T use this or me, but I find it makes things much clearer to read - it gives the scoping and it also provides the intellisense more easily when actually typing code.
>
>To some degree guidelines are just that - guidelines. But I've found that the .NET guidelines actually make good sense.
>
>+++ Rick ---