How much work is being done on the system? Is it done or near done? I think switching to 6 just for the sake of "staying current" is not a strong reason if the system is not changing.

As far as risks, I think a relative question is "Can we access the same set of data from both VFP 5 and VFP 6 without difficulty?" If this can be done, then they can try a new re-compiled (with 6.0) program and use it and if they experience problems, they can revert to the current version (developed with 5.0). When we went from 3.0 to 5.0, we did a fair bit of parallel testing "just in case."

We have actually just started the process of going from 5.0 to 6.0. I have just ordered Visual Studio 6.0 today. I figure most the bugs must have been worked out by this point... Anyways, we are doing this because we want to look at some of the Internet capabilties and some of the new features, but our system is always being enhanced as our industry changes. We would not be changing development tools if the system was in purely maintenance mode.

Joe



>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