No problem. Happy to help. I started in VFP and moved to VB & VFP in about 1997 or so, and I probably work 50% VB, 35% VFP, 15% SQL these days.

I haven't made the move to .Net yet, but it's pending....

VB really isn't so bad. As I said, my own problem is with GUI design in VB, but in terms of business code, etc., it just requires a somewhat different mindset at times. I know people get frustrated, but it's just that code re-use is handled in different ways. You can still get loads done. So don't give up too easily.

Expanding your skill set is a good idea. Here in New York, at least, the VB market is thriving (especially dot-net but even classic VB) but VFP jobs seem more rare. This is all anecdotal, but as a contractor, I do keep my eyes open on these things.




>Thanks for the info. I have been programming for 33 years and the last 6 in VFP, in fact VFP was my first OO language. So I am sorry to bother you guys with this elimentary stuff, but I think its time I need to start expanding my skillset (Not many calls for VFP/Cobol/Dibol/RPG/Assembler). I will be working with VB.Net soon and I understand that the OO characteristics would nearly satisfy a OOP purist.
>
>Thanks
>
>Glenn
>
>>>Does this mean that to pass an object reference from within a control method I would pass the control name?
>>
>>
>>No, you would pass the control, and then, in the receiving method, refer to the object parameter name. Very similar to VFP.
>>
>>
>>>Also how does VB handle containership?
>>>
>>
>>
>>Very differently than VFP. You have forms, just like in VFP. And, there are some visual controls with a rudimentary hierarchy, like some of the add-on grids. But, if, for instance, you wanted to add two text boxes and two labels to a first-and-last-name control, you would need to create the control as an ActiveX component, and then map whatever internal items you would want to reference to public properties on the outermost control. Ugly stuff.
>>
>>This is partly why I rarely develop front-ends in VB. I think that an awful lot of people on the UT treat VB unfairly, except when it comes to visual controls. In those cases I agree that VB feels like a word processor compared to a tool like VFP.