Well, VFP7 will be out in early June so you might wait till then.

VFP7 has a lot of developer productivity features that can't be beat. Sell the productivity features in terms of cost to buy software VS cost of developer time saved.

Furthermore, developers don't want to work in old technology. They will want to leave the company. Would you want your DOCTOR using old technology on you? They are pennywise and pound foolish.


>Hi All,
>
>I've recently been trying to convince one of my clients to move their system from VFP 5 -> VFP 6.
>
>They're hesitant because as far as they're concerned everything works fine and they can't really see a benefit. I'm sure that makes sense to everyone. What doesn't rest well with me though, is that they're running on old technology. I'm trying to formulate an arguement to convince them once for all but I'm stalling for ideas that sound convincing. They want to know what benefits they're likely to see and more importantly what risks they are exposing themselves to. It may help to say that this is an in house development team who are supplying systems to their billing & contracts department.
>
>Also, they've asked me if MS still support VFP 5? Any ideas?
>
>Regards
>
>Paul Robinshaw