>I have a form where I remove an object and then reinstate it. Once I convert this into a class, it causes an error which the generic form does not. The program executes a removeobject of an ole object (MS Web Control). In the form, the object disappears. In the class based form, the object remains. Can anyone explain why?

Is the error something like "belongs to parent class and can't be removed"? I've seen this with grids which had more columns at the class level than needed. Can't kill them, because they're in the class definition. In case you instantiated more objects of this class, Fox keeps the class definition in memory intact, so you get this limitation.

You better start looking for a workaround... first of all, why are you killing and then resurrecting an object? I figure this may be because of some other problem - and we'd better solve that one.