Hi,
I think I figured out the problem. When I disposed the grid I had not removed it from the tabpage that it was a child on. I changed that so it removed the grid before disposing the grid and that seems to have resolved the problem. I am not sure why it ever worked!!
Please remove my zip file.
Thanks!
>The application is rather large, in the neighborhood of 10 meg with they needed runtime files. I will upload you the code that deals with the grid.
>
> The way it works is the application starts upand initializes all the windo elements except the grid. When data is first loaded into 5 related tables with aproximately 1,1,1,50,8000 records starting from the top level to the bottom level table. After the data is loaded the GridgroupingControl is created and the dataset and top level table are assigned to the grid. When the user requests another set of data be added to the tables (all inserts) the grids is eliminated by calling Dispose before the data is added. This is when the exception occurs. This was working at first but suddenly broke with the above message.
>
> Please remove the zip file as soon as you can because the code is propritary.
>
>
>>Hi Bill,
>>
>>Please refer to our shipped browser sample ''GroupingPerf'' [ \\windows\Grid.Grouping.Windows\Samples\GroupingPerf ] which demonstrates a way to add / remove records in the grid using engine optimization technique. Also provide us details on your application and also more information about disposing the grid in your project, if possible upload us sample / code snippet.
>>
>>Best regards,
>>Madhan
>>
Exception4.zip