Interesting. So if I understand you right, it's the overall skills of the developer and not any particular language, right?

Also, you say that Chesapeake is a Fox town, so is Fairfield, IA but what about the region. Do you see direction to preferences there?


>Well I think it's really the IT mgr pref. Unless its a contracted/consulting bid in a shop with no IS/IT dept. Then, I think it is the contractors opinions and/or available skillsets. I know that I only briefly used Delphi and have used VFP extensively. I would be more likely to make a VFP project.
> More money. That is an interesting question. I have seen that the combination of skillsets earn way more than the individual skillsets. I have not seen significant salary differances based on the language in actual practice. It seems that time in carries the weight. The actual ranges of pay that I have seen here (South East Coast, USA) is 16K/yr - 125K/yr with the bell curve hovering in the upper 20's thru the mid to upper 40's.
>
>>Not ranting, expounding.
>>
>>Do certain projects get streamed to PB and certain one to VFP and yet oters to VB or is it more the IT manager's personal preference?
>>
>>Which ones pay best?
>>
>>>Actually, we have a large PB community, but I think overall this is a foxpro town. I actually prefer the fox code to VB code myself. But, I abhor the foxpro IDE. What a piece of crap. They need to do some real work on the developers environment. We need a break (and release ALL the crap) button. Where as VB I hit the cute little stop button and everything goes away. Another thing I like about VB is the find. You can limit your search or say whole project. VFP is in the hurt locker for this. The 'all objects' option is nice but you still have to open every stinkin form. geez! PB lets you search the whole project doesn't it? The Visual C++ IDE is still by far has the best IDE I have seen for finding and organizing stuff in the open project(s). The developers developing the languages that the industry use really need to look around at the other products and get some of the better ideas implimented across the board. Anyway, I have ranted enough on this... :)
>>>
>>>>It hasn't my experience in PB 7 and I agree that it tends to be Ford vs. Chevy to a large degree. What is the market like in your area for either of them?
>>>>
>>>>>This was v3.x I believe. Like I said it was back in 96/97 and I never looked at it again. Sometimes these questions are Ford vs. Chevy questions that may have no truly unobjective views. I can only hope that PB is better now than it was then. BTW: VB wasn't very nice back then either.
>>>>>
>>>>>2 cents,
>>>>>
>>>>>>I have PB 7 and it doesn't seem like that. What version were you reviewing?
>>>>>>
>>>>>>>The problem with powerbuilder (in 96/97) is its debug environment. It was so bad I never went back to look at it again. It was just horrible. You ever see the look on a VFP programmer's face when you show them the F8 key in VB, modify the code on the fly, change it back after your execution line passes. All this in the same window you code in. That same look is the look the PB guys gave me when I showed them the VFP3 debugger/tracer. Thats sad. But, opinions are like diapers some are clean and some are full of stuff. ;}
>>>>>>>
>>>>>>>
>>>>>>>>Thanks Guy. It seems that there as many opinions as people to give them.
>>>>>>>>
>>>>>>>>I'm still curious about Powerbuilder though.
>>>>>>>>
>>>>>>>>
>>>>>>>>>>Why would I use VB instead of Visual Foxpro, Delphi or Powerbuilder?
>>>>>>>>>>
>>>>>>>>>>TIA
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>Keep in mind that you'll have tons of different answers mostly tainted with personnal opinions.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>Here's mine:
>>>>>>>>>VB: Swiss Army Knife of development tools. Can do lot's of things. Not OOP.
>>>>>>>>>VFP: Fast with desktop databases. Full OOP.
>>>>>>>>>Delphi: Between C and VB. More code to write. Faster. Full OOP.
>>>>>>>>>PowerBuilder: Can't comment.