>>I'm still a little confused on how your idea of using local and remote views would actually work. Wouldn't I have to change the control sources? If I have myremoteview.myfield for a control source I'd have to change it to mylocalview.myfield when switching between backends right?
You can USE mylocalview ALIAS myremoteview to avoid this, or have a separate dbc for the remote views. Using a separate dbc for RVs opened with CONNSTRING means you can burn the dbc into your app so there are no dbc contention issues either.
To assist with views against both local and remote tables you could consider xCase which will take care of the details for you- including against Oracle and MySQL if that's useful.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
