I assume people / like myself suggest using SQL vs flat files (dbfs ) type files,because of the overhead / network traffic overhead required for windows file sharing using the internet.

To open a file (dbf) over the internet from what I understand is the at least the entire index file is tranmimitted automatically to the remote workstation, So if your files are quite large, it can slow down performance. Mapping driver over the internet, does require either a VPN or or static IP's and a fire wall unless you want complete access to anyone out there on the net.. (which is not really safe)
Whereas with server based files, they handle communication differently,
the Database is password protected, and each querry, or session can have embedded passwords into it. But more imporantly, SQL servers work in a message response method where a sql statment is sent to the server, and a response is sent back, the respons is usually just the data you want.

But far be it for me to suggest what is best for your application. Have you been able to map a drive over the internet yet and open a inetnet mapped drive ? thats the first step. and then start working with your data and application using data which is stored on a file server (at a remote location). Only then will you get a real idea of if it will work or not. Keeping the application on the local machine and data on a remote machine is what you need to start testing.



Bob Lee






>Im using the internet to connect. The client is VFP not html. I don't know why people keep suggesting sql there is no advantage in doing this. It doesn't have anything to offer over VFP. Either way the backend has to stay in VFP, there is already another app in VFP that will be sharing the data.