Whitney,

If the main reasons for using SQL-server or other SQL databases are size and security, and you have none of these listed as your needs, why move? Why do a lot of work?

Speed comes from proper indexing. This can be done without any changes to your application.

Providing data to other applications can be done within your app with COPY commands, or others can access your data through ODBC. Again, possibly no changes to your existing app.

Now, the suggestions about views are especially important when designing a new application which will start with VFP tables and move to SQL databases in the future due to size or security issues.


>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.