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

Oh wait, you don't actually own a copy....nevermind...

Why is it again you are commenting on something that you don't actually use????



>You might want to apply the technique I described in another message: Replicating the data from SQL -server into a VFP database. This way you ensure that every update is also updated within your local VFP table and have the performance advantage of the VFP local database engine.
<