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?

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?


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


reasons for reluctance to MS SQL
1. have to learn another system
2. referential integrity triggers may have to be coded by hand (no wizard/builder/visual referential linking?)
3. table creation may have to be coded by hand (no interactive builder?)
4. Server-based stored procedures using SQL syntax instead of VFP procedures
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.

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)

Thanks in advance for your reply..