>>>>>>I have an application that relys predominantly on remote views. An older copy of this application is running at a sight on the east coast.
>>>>>>
>>>>>>I have made modifications to the local application and would like to distribute the new app to the other site. The problem is that I have modified existing remote views and added views as well. Since these are contained within the database itself, how can I distribute just the views without overwriting the existing database?
>>>>>>
>>>>>>Hopefully I am missing something simple.
>>>>>>
>>>>>>Thanks,
>>>>>>
>>>>>>George
>>>>>
>>>>>Distribute dbc related files only (don't distribute dbf/cdx/fpt files). Surely, I would recommend to have pilot workstation to try.
>>>>
>>>>A good rule to follow is to place all your remote views in their own container. Since views do not have hard connections to tables you can simply distribute the new views container without worry of disturbing exsiting data.
>>>
>>>How do I put them in their own container? When I create views either through the GUI or programmatically, they are saved within the database somewhere (as far as I can tell). For instance, if I create a remote view using the wizard and then save it, it only asks for the view name and not a directory.
>>
>>I guess the advice was to create separate dbc for remote views only when you will start your next application from scratch. Right now, you, I guess again, could proceed with another solution.
>
>The only solution for the application at hand is to write a utility to programatically add the views to the dbc currently being used. It will have to use dbsetprop() to change settings to the desired configuration like 'Send SQL Updates'.

Why he cannot just replace dbc/dcx/dct files leaving existing dbf/cdx/fpt files?