>>>why would you want to do that?
>>
>>I have a form form that was saved as a class a long time ago by another developer. It has a lot of code, and member objects. I don't like composite classes at all, and the reason this form was saved as a class in hte first place was so it could be used in 2 different implementations. It just turns out that if the other developer would have put some strategic thought into it, the same form could be used for in both places.
>>
>>Now that I am having to maintain the form, the fact that it is a class and not a vcx is turning into a huge headache.
>
> I can't say I've done a whole lot of testing here, but it looks like I was able to change a class back to a form.
>
> All I did was open the .VCX, and changed the first Uniqueid field from "Class" to "Screen". Then I saved it and copied both the .VCX and .VCT to a different name with a .SCX and .SCT extension. It let me add this new form to my project and modify it.
>
> Seems too easy. I'm wondering about what might be missing or won't work.

I converted many form classes to .SCXes this way and didn't have any problems with the new forms.

Nick