I am out of ideas as well.

I had a grid working fine. I went to the parent class of the grid and wrote a setall() routine for text boxes on a grid. I had added a property and a method to text boxes. I ran the app and received an error on the setall() command and realized that the grid was pouplated with Foxpros baseclass text box not my text box class. I added my text boxes to the grid now having two. I was going to delete the original. Through all of my testing I have a mess. I was able to hack the VCX and change the parent class of an original grid text box in one test.

It looks like I will have to go to backup tape and start from there. I will hack the VCX and change the parent class for the text boxes. I hope that someone post a message explaing what is going on. I would like to understand.


>Ron,
>


>This is very strange. I see that Dragan pointed out that you can't delete an object at design time that's part of a class definition. However, I just tried this and got an error message. I'm out of ideas. Maybe someone else can suggest something.
>
>>Absolutely, I almost want to start over on this grid but I would rather know what is going on. Is there a SET DELETEGRIDOBECT OFF or anything like that :)
>>
>>>Ron,
>>>
>>>That works for me. Are you sure you're clicking only on the title bar of the form, not the form surface, the grid, or anything else?
>>>