Dragan,

The problem persists. Moreover, we found a strange thing: all our classes show the parent class in the classlib property in the Properties sheet. E.g. for example, CalendarObj from aCalendar library shows Calendarobj in the Class property and c:\mmviscollect\libs\abusiness.vcx as Classlibrary property. Is it right? Should not it show aCalendar.vcx instead? Can you please quickly check any of your classes?

>>Martin,
>>
>>I think, something really serious happened with my computer and I don't know what to do to fix it :(
>>
>>We're using MereMortals framework. When I try to use builder with my class it gives me the error message that dataenvironment class could not be instantiated. I created a new library, moved the class there, created a new DE class and I'm getting the same error messages again.
>>
>>But moreover, I tried with my colleague's classlib and I'm receiving the same error messages. However, the same classlib by my colleague works on another machine. I also noticed that I open that class, try builder, receive an error, exit the class without saving, but the timestamp for VCT file changes, while time for VCX remains the same!
>>
>>What happens? Looks like I may need to re-install VFP or apply some other drastic measures.
>
>I've never worked with MM, but since it's a CodeBook type of framework, my first suspect would be the metadata. Are you using a copy of metadata? I'd first try to replace it with a fresh copy of what your colleague is using.
>
>And recompile all the vcxes.