and if i wasn't crying before... I am now.

If only I had tried that first. Then I wouldn't have spent so long trying to recreate a wheel that didn't need recreating.

*sigh*

Thanks Naomi. Next time I think I'm having a good idea... I'll shout first!

;-)

>>Ok,
>>
>>I can see I'm going to have to digest that. It seems like I might have to go the custom control route as I don't think I'll be able to bind to the events in the grid.
>>
>>I'm guessing of course, but that's based on my observations and the reason I've resorted to coding the grid. As my control source is a cursor, I didn't want it to be displaying deleted items and potentially chewing up a lot of memory holding deleted items either, so when it came time to redisplay the grid again, I just recreated the cursor.
>>
>>So when that happened, all the embedded controls and header names etc disappeared. So my thinking is that the same thing would happen with any code I insert into the grid events.
>>
>>Does that sound logical to you?
>>
>Can you have a predefined cursor for the grid? When you need to refresh your data, you select into the temp cursor, zap the original, append from temp and refresh grid. Then you don't have to worry about losing controlsources, etc.