Hi Garrett

Your suggestions did not fix the problem but I did discover the cause.

I was trying to create a class that would be a drop in replacement for a text box but would have some capablities on changing the way text was displayed. It had a hidden text box bound to the data and a visible text box that showed the transformed value. So I was adding properties to the container so that the container interface would match the standard text box interface and thus could be dropped into an application where a textbox was used without requiring re-writing the code for controlsource, statusbartext etc.

However, adding properties like controlsource, alignment, fontname, fontsize, fontbold, value, readonly etc. to the container appears to cause this problem. Once I removed all these custom properties from the container I no longer get the the error.

If you are unable to use standard property names for custom properties how can you design classes with a standard interfaces that could be used to replace the standard VFP controls?

Thanks
Simon


>>I had the same error again only this time I was not adding
>>a property I was simply scrolling down the object properties
>>window while it was combined docked with the command window
>>and datasession window in a tabbed page format.
>
>< sigh > Lovely.
>
>Have you tried trashing all copies of FoxUser.dbf to make sure they're not corrupted?
>
>Also, if you turn the hardware acceleration down in your Display settings, does the problem go away?