I hardly thin a $400 product cost is a consideration in a $400K five year project, but you could skip it.

If you could send him some code it would be very helpful, he has a long road ahead and could use the help.

I think you are doing him a bit of a disservice by minimizing how big a change this will be for him, IMHO

Bob


>>My suggestion of moving to VFP9 was primarily geared to the improved syntax for VFP SQL that would be more compatible with .Net when he makes that jump.
>>
>>Especially since most of the stuff he has is Use/Scan/Seek type of programming, the conversion should be very fast and clean if not fully compitatable. This way he would learn better SQL syntax as he starts to do that.
>>
>>He should get a copy of VFP9, point the project at it and compile, and see what happens. Chances are good he can upgrade VFP versions with very few lines of code and might not require any change at all.
>>
>>Bob
>>
>>
>
>My bet is that it will be a nightmare. I moved a project from vfp 6.0 to vfp 8 and it had all kinds of incompatability problems. There is no need for him to spend the 400+ bucks on a dying product to move it to .net. No need.... I can send him all the vfp 6.0 code he needs to make his data layer and convert to .net from there.