>>Way to complicated and more of a pain to manage. Also, in many cases, going to VFP data is not an option. Tell you what, go to an IT guy who has made an investment in SQL Server, and tell him that to get the best performance, you need to use VFP. If I were the IT guy, I would pick you up, and throw you through a window..
>>
>>Most VFP folks insist on taking a VFP-data mindset to SQL Server. Instead of telling the guy to use a VFP crutch, you should tell him how to use SQL Server properly....
>>
>
>Well, AFAIK replicating data locally for speed is an accepted way to optimize CS systems.....

Sometimes we force VFP on our clients. John is bringing to fact that they want to use SQL.

I disagree with replicating data between VFP & SQL. That's not optimizing, it's only a crutch. I have found that the people who are SQL only are serious about their decission. They have invested alot of capital in equipment, software and licenses. I would try to do what the client wants his way, and allow VFP to manipulate the data my way.

Moreoften the biggest issue for VFP is security, in that there is none. SQL you have some very substancial security. Don't tell me about Encrypting data because that's not security, it's duct tape.

__Stephen