>Hello all,
>
>I'm just curious to see what's exactly the advantage of using VB over VFP or just using VB at all. Almost all my VFP colleagues and friends do not like it at all after trying it for a while and I haven't just had any time, interest, or opportunity to really have to use it.
>
>I'm saying this just because we just had a sour experience of having to outsource development for a very big client which chose to have their system done in VB instead of VFP. The reason? Because there are more developers that could 'carry the flag' in whatever event could arise.
>
>After a while these guys (3-4 yrs experienced and working full time for good companies) put together a very lame interface, really awful grids to 'browse' the data, very slow data access (the main data is pulled from a SQL 7 database using views ~ 50000 records) and so forth; just crappy stuff everywhere, which it ended up delaying the deliverance of the project for more than 5 months (and still counting)
>
>We did try to show these people what we wanted to do, but we were all having a hard time trying to achieve some of the features that we could get in a snap using VFP.
>
>I see there's many more jobs postings for VB developers than for VFP's but I really have NOT seen ONE VB app that I can really say I could take my hat off, when I have seen many done in VFP (and this is only locally, here in Edmonton and Calgary)
>
>So, really, what's VB really good at and why does it have such high demand?
>
>Thanks
>
>Note: VC++ fans need not to worry, I know a few things what this one can be good at

Hi Gil,

VB can create and raise events. This is important in middle-tier COM objects. VFP can't do this.