Just like us!

I worked with a gal a few years back who enjoyed my "stirring up the pot."

What is great is that they see it as a hinderance and wee see it as a necessity.

Here is a return line for you to use at any time. "They don't call it Visual Advanced do they?"

__Stephen

>Stephen,
>
>Just wanted to let you know that I copied this message and sent it to a couple of VB guys here at work and it started WW III. Those VB people really take offense whey you start putting down there development tools.
>
>Jeff
>
>>I just got the new Software Development and I had to LOL while reading the departments listings. Bob O'Brien has a short article on "Simulating Inheritance."
>>
>>"You can easily compensate for VB's lack of inhereitance, but you might find that you're better off without it"
>>
>>In essence he says thay you could create a procedure file to hold all of your older version code in case you needed it.
>>
>>His closing lines are, "I've participated in several projects (using other languages) where relying too much on inheritance became a major problem. Visual Basic's Lack of inheritance helps limit such errors."
>>
>>That's what I love about Microsofts Flagship Product. They keep all the really hard stuff away from the people who could do the most dammage.