Thanks but the application is installed in over 100 clients and the process of detecting a broken dbc and recreating the remote views needs to be automated.

Rgds

>>Thanks for the suggestions but all this needs to happen on the client's PC.
>
>Actually, it doesn't - make a copy of the client's DBC, and install it on your own system. Install SDT and register it's metadata on the developer's machine. Use eView to modify the RVs, run SDT's database explotrer, and freshen the metadata.
>
>Write a small app using the SDT runtimes that will run on the client site. Send this plus the updated metadata to the client site. Run the app against the client's DBC; and invoke the Update method - this will cause the DBC, tables, views and indexes on the client system to be brought into compliance with the metadata you've supplied with all the new view and index information. When it completes, the client's DBC will be functionally identical to yours because its structures have been updated via SDT.
>
>>
>>>>I was hoping for a simple method of opening the DBC and trapping the error so that the RVs can be automatically recreated. To recreate the RVs I use :
>>>>
>>>>CREATE SQL VIEW "XXXX" ;
>>>> REMOTE CONNECT "SQLCONN" SHARE ;
>>>> AS SELECT * FROM xxxx ;
>>>> WHERE xxxx.key IN(?goAPP.gnKEY)
>>>>
>>>>I was hoping for large tables I could limit the "SELECT * " to just one record.
>>>
>>>Download a copy of eView and buy SDT.