>>But seriously, VFP 3 did leave a lot of boboos in its samples
>>and custom classes by the time of shipping.
>
>this is because it was shipped in a hurry - this is why vfp3.0b was shipped
>anyway IMHO VFP5.0 is what we should have got originally with 3.0 :)
>
>Arnon

Totally agree. A lot of glitches from VFP 3 started making perfect
sense once I got my hands on 5. BTW, remember I was bugging everybody
with sharing methods/control arrays? Well, I found out that I don't
need to use control arrays and still accomplish the same task I was
going after to implement method sharing. In fact, it follows exactly
the same (almost) concept as other OOPL's. So, I am home free again :)