Technical issues aside, the biggest thing you need to change is from a FoxPro mindset to a Remote Database mindset.

For example, suppose you have a table with 500,000 records. In FoxPro you can USE TABLE and BROWSE and voila, there's records on the screen.

In SQL, if you try that it can take a long time to SELECT * FROM THATTABLE before you BROWSE.

So IMO the big trick is to always provide some kind of where clause to the select statement BEFORE you ever look at data.

In other words, you switch from "grab all data and filter it later" to "never grab all data and always filter first". There can be quite a bit to this switch.


>Hi,
>
>What would I need to setup an application to store data into tables on an SQL server?
>
>I would obviously need a server, Windows 2000/2003, Microsoft SQL? Oracle?, what else?
>
>What would I need on the workstation side?
>
>How would I setup my development system in my office?
>
>I know these sould like silly questions, however, I need to save data to SQL tables and the application currently runs FOX2X tables. All advice is appreciated. Thank you in advance.
>
>Kind regards,
>Derek