>>
>>Basically, yes. I'll prototype in VFP, but that's frowned on. Unfortunately, I've been lied to. I was told by the PHB that I'd be given every opportunity to demonstrate why VFP should be used in some situations. I haven't had that opportunity.
>
>So PHB pushes you to the "dark side". :)
>Seriously, it sucks. It's one thing to change developmenyt tool because of technical reason, another for political.

Sergey,

I don't know about you, but I'm getting sick and tired of fighting these battles. I told the PHB that I, by myself, could roll out a Costing System (currently in FPW 2.6) in four months.

The system did much of the work that an existing PB 6.5 app did in terms of calculation. When I wrote an in-process COM DLL to do the heavy lifting, I was told that it was "wrong". The problem was that PowerBuilder blew up because it couldn't handle the IDispatch interface.

Now the original implementation of this took 14 months with 5 people. Then they updated it! I told them that if the object blows up when calling the ReInitialize method (to set the properties to their defaults), destroy the object and re-create it.

Well, the re-write, with at least two people took seven months. So stuff I'd written 10 years was basically blown off.