>Here are a few reasons you might want to switch between local and remote data:
>
>1. You may want to develop an application that uses local data but be able to move to a client/server solution in the future.
>
>2. If you're writing a commercial product you may want to offer a version that works with local data and one that is client/server.
>
>3. You may want to prototype or develop an application using local data. This is useful if your developers aren't always connected to a database server. This becomes less necessary with products like SQL Server 7.0 that will run on Windows 95.
>
>>My colleagues and I are evaluating the MM framwork and codebook in general. One of the questions raised was why would you want the ability to switch back and forth between local and remote views. After thinking about it, I am wondering what the real advantage of this is, too. I know this ability is much touted in the framework, but I can't think of a realistic reason why you'd want to do it.
>>
>>Knowing the thoroughness of codebook methodology, there must be something I missed. Can someone explain it to me?
>>
>>Also, what is the real difference between the refresh and requery functions in a view?
>>
>>Stumped in The Bronx


In client-server development, SQL-passthrough is used often, but in a local version of an application, it can't be used. How do you rectify this in Codebook? You would still need two versions of code-- client-server and local.