Actually, it should be only one change. Change your app to use remote vs. local data. You can do this through the preference form, or directly in your registry (if you use an ini file, check the user guide for instructions on best practices for changing that file). As long as you've followed MM view naming standards for -- 'lv_' for local views and 'rv_' for remote -- this should be all you need to do.

Since we juggle multiple dbcs, we had to apply extra custom code. Let me know if you suffer likewise and I'll point you in the right direction(s).
---J


>I'll try playing around with this - thanks for the insight. What kind of tweaks would be required?
>
>>Actually, you don't need to move to SQL for creating remote views or for a speed difference.
>>
>>To test, set up a remote connection to your dbc and create a remote view that mimics one of your slower local views. You should see a marked speed improvement.
>>
>>You'll have to tweak the framework a little to accommodate remote vs. local views, but it's relatively straightforward.
>>---J
>>