Hello John,
>>VB is only Object Based and will never be OOP. Some VB guys, especially new >comers think it that way - VB is OOP - because it's a 'Visual' programming.
>
>So what? It lacks inheritance and a decent containership model. Ever hear of the old saying - "Don't throw out the baby with the bath water". Folks who scoff at VB in this regard - picking on the fact that it is only Object Based - probably have not looked at - or worked with the product to any serious degree.
I just give intuitive counselling (sounds like a counsellor) with the ignorance of some VBers who are blind folded walking in the programming community.
>Don't get me wrong - VB has its limitations - so does VFP for that matter. But, does that make them bad tools? Of course not. Each has a purpose and unique strengths - and weaknesses.
I definitely agree.
>Also, how do you make the conclusion VB will never bo OOP. Do you have some secret knowledge that none of use possess??
I am only speaking on VB's current structure. Ofcourse, MS can do it OOP but as far as humble knowledge is concern, it is a total rewrite.
>VB is not OOP - but you can employ OO design techniques with VB - even if it does not support inheritance to the degree that VFP does. I won't go as far to say that you can do full OO programming with VB. You need full inheritance for that. But, you can come close.
I agree, but not as easy as VFP's capability
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net
CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."