I have been working on this all morning, and I am seeing a problem using the Name property. First I have a grid using these _Header and _Column classes on a form. I then make a change to the GridMembers PRG file. If I then run the form, the default VFP HEADER baseclass is used. If I remove the Name properties from the _Header and _Column, all issues go away.

I can live with column names like _Column1, _Column2 and header names of _Header1. I can use the Code References tool to find all occurences where these may need to be changed.

>For generall purposes its fine.
>
>I run into 2 problems with that behaviour
>
>1. my errorhandler reports wrong class
>2. the point where I trap into that was a SETALL('DYNAMICBACKCOLOR',..,'_column') command.
>
>To me the biggest problem is, that if I use not only one class in one object, I can not see the origins and can not use SETALL to change a specific group.
>
>The problem with the caution in the help file will raise if VFP needs to reload code from the prg. This reload will be based on the class and classlibrary of the object. I have no idea what I need to do to force such a situation. May logic says that this will be bound to internal memory handling.