Hi Victor,

As long as it work uh... :)

Your problem is really that you're moving from runtime to development. In development, if you want to change a class it should not be "open". Now by "releasing" an instance you're not necessarily releasing the class definition that still might be somehow "loaded" in memory.

Your best bet is to issue a "set class to" and a "clear all" at the end of your startup program, well after your read events, but make sure that happens as next to the last statements.

Because if I'm right, you now solved your problem for this class, but you may later find out that you have the same problem with others. "set class to" will close all the classlib definitions you may have opened and clear all will clear all the variables and the class definitions.

I close my programs like that and I never have your problem (anymore). So as we say in the lower countries : "Baat het niet dan schaadt het niet".

Take care and HTH.

Marc


>I added this line to the loop wich closes all the toolbars
>clear class (.aBars[lnI, 1])
>
>Am i doing the right thing here or am i now making the symptom go away instead of the decease
>
>I'm still wondering why the error message doesn't occure with baseclasses for forms.
>
>thanks