See my replies interspersed below:

>i've read that the reason for use of MS Sql server database is for security, reliability and online modifications.
>1. security- being based on a file server, vfp files are exposed to all users.
> my question: can a copy of vfp run in the server and wait for 'queries/commands' from a front end vfp running in the client? is there a mechanism for communication between vfp/server and vfp/client like between sql server and vfp running as client (sqlconnect, sqlexec), so that the databases can be kept at server without being shared and the vfp running on the server just sends the query result to the vfp running on the client?

There are ways to do this. One is to have middle-tier business objects that reside in COM+, then access the tables using a user id different than that of the user. I have some COM+ articles on the MSDN web site (linked through my web site) and will be presenting COM+ topics at both the German DevCon and Southwest Fox.

>
>2. reliability- the main reason sql is more reliable may be because the files and indexs are not opened by multiple computers and the sql files themselves are only opened by sql running in the server.
> my question: aside from the reliability bec of the setup/achitecture of a client/server system, are ms sql files really more stable than vfp? say both sql files and vfp files runs on a standalone computer and we test it by switching off the power (not properly shutting down windows) for a very lot of times.... eventually does vfp files get more corrupted while sql files does not?

I have had very little DBF corruption in recent years. Buffering the data helps tremendously with this. What corruption has occurred can be traced back to bad network components or bad user habits such as turning off the computer without exiting the application.

SQL Server is suseptible to corruption too, but as you mentioned, because the user never opens the files directly, there is a lower probability of corruption. Bad network components can still cause it.

>
>
>3. online modifications - sql databases/tables can be modified even while in use while vfp need to be used exclusively before modification/index creation
> my question: are the current vfp or future vfps going to incorporate such capability?(being able to be modified or index creation while table is in use..

I don't see this happening. It's simply due to the file-based nature of the tables. Access has the same issues.

>
>
>reasons for reluctance to MS SQL
>1. have to learn another system

There is nothing wrong with learning something new and SQL Server is a great product to learn.

>2. referential integrity triggers may have to be coded by hand (no wizard/builder/visual referential linking?)

You can setup foreign keys and have SQL Server handle some of it for you. The coding you need to do is quite simple.

>3. table creation may have to be coded by hand (no interactive builder?)

MSDE doesn't have any admin tools, but standard SQL Server does. In SQL Server 2000 you can use Enterprise Manager. SQL Server 2005 has all new tools that are pretty good.

>4. Server-based stored procedures using SQL syntax instead of VFP procedures

Nothing wrong with that. T-SQL isn't that difficult to learn. There are some good books that help.

>5. connectivity issues will be a hassle.... such as returning 100 records at a time (there's workaround solution but that's the point..).. timeouts,etc.

You need to rethink data access. With VFP, you typically get the entire table. With SQL Server (and other server-based systems), you get "sets" of records. For example, "SELECT * FROM Customers WHERE LastName = 'Smith'". The standard prev/next buttons on the form then work only with the selected data.


>
>I'm currently a programmer using vfp, but I've not yet began seriously learning/applying vfp-MSSQL type of programming...i'l definitely go along with learning mssql even if all my clients have networks < 30...the main reason is the capability of modification of tables w/o interrupting work of clients. stability(incorruptibility) is another major factor. the security consideration is a plus, although no problem with current clients regarding file server system. HOwever i think i'l be missing the vfp database designer visual environment... i'm wondering if ms sql has a drap and drop/drawing visually creating relational integrity and the no-programming needed relational integrity builder..(with the combobox of cascade/ignore etc)

Don't bother with MSDE as it doesn't have any GUI tools. You can download SQL Server Express 2005 beta for free from the MS web site. It'll get you started.

>
>Thanks in advance for your reply..