> Once you've asked about this, I also decided to move 2 of my Treeviews to > other VCX files (they were not located at the best place). And it worked > fine. > > I suppose your Treeview was, as mine, saved as a separate class on your VCX > (not as a part of a bigger class such as a container or a Form, because > then it'll be very easy - just cut and paste the Treeview directly). Well, it was created as a class... and then used in a form class within the same .vcx, which originated in the main vcx where it was designed to be saved if it all worked ok; just couldn't move it there when I wanted to. > These were the steps I've done, all at design time: > > First, create a new Form. Then you add to your Form Controls Toolbar the > VCX file that contains the Treeview you want to move. Next, add the > Treeview to the Form, select it and choose *Save As Class* from the File > menu. And that's it. Just choose there the new VCX to store the Treeview. > Close the Form without saving. Good old click & point programming :) Never thought of that. Thank you, it worked just fine. > One important thing is that, even after all of this, I had to open the new > VCX file as a table to correct the values at the fields CLASSLOC and CLASS. > Those values were wrong (my Treeviews are children of the Project Treeview > Class, which is child of the Base System Treeview Class). I wonder what would it do if I just renamed tmp.vcx to something else, would it be able to find the reference within the same .vcx where it is... I'll try that tomorrow. 10Q again, one nightmare less.