>I haven't read the full thread, but most of the first level answers.
>
>The one big difference between SCX and VCX is, that you can subclass VCX forms of course. You need to SaveAsClass a SCX to do the same.The big advantage of SCXes is that you simply can DO tehm, or Run them from the standard toolbar, that's quick developemnt and testing.
>But all you need is a function and you can do about the same with form classes.
>
>Fabio has a point about the evaluation of properties, others mentioned the Dataenvironment difference, but to me OOP is the main difference, anything else is quite the same.
>
>There's one thing though, that you can do in a SCX at design time and can't on a VCX:
>-Create a new SCX form
>-Drop some controls on it
>-select them
>-choose "Save As Class" from the file menu
>
>You are now promted with a save as class dialog with the top option being to save the selected controls only as a new class. This will then be saved as a container containing the selected controls.
>
>That's a nice feature, but one you won't need that often if you already have your libraries of basic, simple and advanced controls.
>
>But the main plus for form classes is OOP of course. You might say that you can do all application forms based on some framework form class. Well, yes, okay. But it's always the end of inheritance if you create an SCX instead of a child form class.
>
>Bye, Olaf.

The question is - is it possible to go back route - from VCX to SCX? I don't see a way.