You have a couple of choices

1) Upgrade to VFP, probably won't require much work especially since you are not currently using a lot of SQL statements now. You can test this by getting VFP9, recompiling your program, and give it a test. There is a reasonable chance you won't need code changes. Then make an SQL Object to pass your data through, then convert the USE/SCAN/SEEK logic to SQL logic.
Next convert to SQL Server, then to .Net. If you have a little bit of staff I would have a programmer learning .Net now so he will have some experience when you are ready and can train the rest of you.

2) You could skip the conversion to VFP9, but do the rest, but I believe this would not save you any time in the long run.

3) You could jump right into .Net, in which case I would suggest a mentor or consultant work with you to make the jump. Without going through the steps above, you would basically be writing a new program with a similar functionality to what you have, but you could take that opportunity to rethink logic, interface, etc and update the look at the same time. Be aware that data handling in .Net is very different.

4) You could hire someone experienced in .Net to do the programming while you concentrate on the functionality and testing. He can train you as you go so after it's done you can maintain it.

Not to discourage you, but where you are at now is behind the times regardless of language used and you are going to be spending quite a bit of time on the learning curve. I personally believe you will need some outside help to accomplish this.

Bob




>Bob
>
>I'm familiar with using VFP SQL statements but the major part of the app is written as Use/Seek/Scan
>
>If I understand you correctly - you are saying convert the app to use VFP SQL statements and THEN think about SQL Server
>
>Thanks
>
>Colin
>
>>Assuming by individual calls, you are talking about VFP SQL calls rather than directly working with the tables (Use/Scan/Seek). If this is the case, the basic idea is to send that SQL command as a string to a single object so that object can interact with the backend. For the first pass the object would just execute the SQL command locally and return the cursor. Later, you can alter that one object to work with SQL Server (or MySql/Oracle)
>>
>>In my case, the SQL Object is on my baseclass form so the cursor ends up in the correct data session automatically. HTH
>>
>>Bob
>>
>>>>>I need to migrate to VFP9 first (yes I know not 100% necessary but desirable)
>>>>>
>>>>>Then I need to move to SQL server
>>>>>
>>>>>Then I need to move to .Net
>>>>
>>>>You don't need to go to vfp9 to use sql server. We have it here in both 6.0 and 7.0. Do you have to move to 9?
>>>
>>>John
>>>
>>>Now that's really helpful - no I don't need to move to VFP9
>>>
>>>Sadly all my table work in VFP6 is individual calls which means a hell of a lot of changes - any tips on putting SQL in as backend?
>>>
>>>Thanks
>>>
>>>Colin