Thank you very much for your answer!

Greetings,

Afier Appelman

>Afier,
>
>Your best bet might be to use a source control program like MS Visual Sourcesafe. With Sourcesafe you can share code between multiple frameworks. You can then "freeze" the code for one application, but not others. When you release an application you freeze its version of the framework code. This way, as you modify the framework you can be confident that your released applications won't suddenly become buggy because of changes to your framework. When you're updating an application, you can "un-freeze" it's version of the framework source code to take advantage of changes to the framework. At this point you will want to re-test the application to make sure you haven't introduced any bugs.
>
>If you don't want to invest in source control software (you really should, though, for many reasons), you can probably achieve the same thing manually by using copies of the framework for each application, but only modifying a central copy of the framework. In other words, there should be no application specific modifications to your framework.
>
>>We are using Visual FoxPro 5.0 and we have build a framework. Of course we want to make other applications from the framework. Now we would like to know if it is better to copy all the framework-classes to the new application or that we will use the classes from the framework directory. In the last case it will be possible that if we change a method in de framework-class, all applications will be changed. We would would like your opinion please.