I wouldn't use more than one together. I was just offering a suggestion, based on what Microsoft is doing. Bonnie suggested using "m_" instead. The most important thing is to be consistent in whatever you choose. It will make reading your code much easier for other developers.

>>A common way of naming Fields that have a cooresponding Property is to prefix the field name with an underscore {"_"}. For the Property name of "MyName" the field equivalent would be "_MyName".
>>
>
>Yeah, I've seen that a lot in C++ code. I hate it <g>. At this point, I'm not even sure I have a rational reason too, except that it seemed to make learning C++ a lot more difficult/cryptic; I kept asking myself: is that a naming convention? Some sort of operator? What's the difference between _Something and __Something (or, heaven forbid, ___Something)? Especially since that's the line continuation identifier in VB, isn't it?