Hi Costas...

What they did is took and printed one whole block. So, the editing process in itself was not through. It gives the impression that I somehow suppoprt the article, but only wished to add some material. In realty, I think the article is about as sub-standard as you can get, and did my best to correct the record.

Folks that don't know too much about VB would not know. I thought it was important enough to stick my neck out a bit and correct the record.

As for continuing to use VFP, you should. However, when your in situations where you want better windows API support, need events, etc, VB makes a good alternative. It is certainly better than having to go and learn VC++.

So, you should learn and know both.

It is important to present this material in the correct manner. I have been the one in the community to lead this whole "learn VB thing" So, I guess I am sensitive to how it gets presented. It is a seemingly easy thing to present. In reality, it is not. On the surface, VB seems like this harmless child. Dig deeper, and you find it can be a complex beast. And moreover, has some interesting attributes that are very different from VFP's.

VB is much more rigid about where you can and cannot do things. VFP is much more lax in this area.

In any case, I hope I have cleared things up for you and the rest of the readers...