>Mark,
>
>You mean you have 5.1g, right? Or am I a whole version behind?
>
>SDT will copy but I may have to make some coding changes to the Copy Table/View code because it want's to have the tables in the new DBC that the views are looking at. However, what I am doing is trying to rip out all of my Views that I created before I learned about contention problems with the DBC on the server and numerous other things like Views getting corrupted by the View Designer (Thanks View Designer!) and move the Views to a Local Workstation DBC. This is also in preparation for going to SQL server for my Medical software. I want to easily (or whatever it takes) to switch between Local and Remote views. I am recoding my framework now to support it and from testing and reading that it is better to have a Local DBC just for my views on the workstation and maybe even wrap it into my EXE and then on the server have a DBC that contains SP's and the Base Tables.
>
>SDT hiccups when I try to copy though because the Local Workstation DBC only has views and NO Base Tables, since the tables can only be contained in one DBC.

You 5.1g. I was using SDT to copy remove views. Yes you will have a problem with local views and no base tables unless you copy them as well. I beleive John suggested running GENDBC to create the code. Then Copy and paste the view code in its own PRG. Tweaking that and running code to create selected views is then quite easy. Then you have the eView tool in the files section here that Erik Moore created to set view properties. Combined, this is better than the VD.