>But the reason I answered this post, is the other part to of your comment, about changing your app to client server.
>
>And in my opinion, its worth it. Very much worth at least starting the process. sql server (any sql server,) is for the most part faster, and more stable
>
>considering that you have the knowldge of working with a Great Front end tool like VFP, going that extra to learn, and setup, what the Big Guys DBA's at oracle, already know, at least for me has been the most fun since I moved away from dos fox, to VFP.
>
>Dont expect to get-it overnight, or be able to rewrite your code in a weekend, its a bit more tricky than that. But I made the decision a few months ago, not to use the DBF dbc file structor a few months ago, for anything. and I am never looking back.
>
>The internet has changed my customers opinion so much, that all they want is more more more. and relying on a network based shared drive solution... Well, is a band aid...the client server, and distributed application market with distributed database shema (sql based) or xml based, is what the future will require. --


IMHO I would have to disagree with this. The problem is that SQL based servers are NOT faster than VFP tables until you get to VERY large tables and/or large number of users. I agree with programming to be ready for SQL based backends/client-server, but the cost benefit is just not there. For one, client-server requires usually an even more robust network, and far more powerful servers as well. Unless you a very large userbase, or VERY large databases it's just not cost effective to move to client-server. You would still need to do the same fixes to the network, and then things would probably be fine unless we are talking insane numbers of users (and VFP tables scale to hundreds of users with proper design). Given reasonable network infrastructure, I would put VFP tables up against almost any SQL backend performance wise. The only thing client-server will give is security, data robustness and and increase in query speed over low bandwidth (providing that the return sets are fairly small).