>Hi,
>
>I am exploring the possibility of setting my VFP app to work with SQL Server. I've reviewed the upsizing and client/server documentation that came with VFP6 and feel like I undestand the concepts, but I'm trying to avoid heading down the wrong path in converting my tables and databases to run in a VFP front end - SQL back end situation.
>
>- Should I use remote views ?? (I've heard there can be problems and not much benefit from using them).
>
>- Should I explore more development on the SQL side (scripts that update data etc..), or concentrate on altering my VFP app data (convert my tables to local and remote views etc...) ??
>
>I know its a little vague, but I was wondering if anyone that had done this before had any input.
>
>I would greatly appreciate any information anyone has.
>
>Also,
>The tables in my app are all 10,000 records or less.
>There are no Local Views in the application.
>Security and Transaction Logging is not really an issue.
>2 main goals are speed and providing data to other applications.

Hi Whitney,

We have our VFP w/ SQL Server app here that we've implemented using remote views and SQL pass-through. I think remote views are the way to go for client/server with VFP, at least for the data entry and update areas. In terms of read-only data used for reporting etc. SQL pass-through is pretty painless. I wouldn't recommend using SQL pass-through for updating backend tables though because remote views handle a lot of the legwork for you.

There are some limitations with the view designer but they are easily overcome by hand-coding your view. For the most part, you should be able to use the view designer without a problem.

Good luck!

-JT