I'ld aim for the same direction, but as first step make certain every data access in the app works via cursoradapter - keep current dbf or use a play SQL server version. That way the decision which SQL backend to use might be left to your successor or a possible buyer of the company while enhancing company worth by having easy upgrade to C/S baked in.


>That's exactly what I am going to suggest to them. They just don't want to be caught at some point in having to do it all in a rush. They know I also plan on retiring in about 5 years so they would like to start the process of getting onto new platforms without having to do a "big rewrite" all at once and in a rush. As well, if we do it a stage at a time while I am still around, I am available for knowledge transfer to the new company that would support them going forward.
>
>>
>>They have had sessions about moving from VFP to .net earlier, and also about using SQL server for data storage in VFP.
>>
>>In your case, I suggest that you first focus on switching into using SQL server for your VFP data, and then focus on rewriting the application itself. Who knows, maybe something else will arrive?