Hi Colin;
PMFJI, but I use the Grid highlighter for forms with page frames and multiple grids. There is a property .chostname in which I specify the grid that the highlighter works with. It defaults to "grid1". If you only have one grid and it is named grid1, you would not need to set this property. I have also noticed the invalid dynamic forecolor or backcolor on release in the past. I think that this occurs when the highlighter is placed on the form before the grid and perhaps even when the grid is edited. I suspected that it has something to do with the order of release causing the grid to be distroyed before the highlighter.

Anyway, I make it a habit to remove (ctrl X) the grid highligher and save the form then paste it back in to be sure that it is the last object(s) on the form. That seems to work for me. I have one data maintenance form that has a page frame with 5 pages with 2 grids per page using the highlighter. It takes about a second or two to instantiate the form and populate the grids, but I have not seen the invalid dynamic forecolor error for quite a while.

HTH

>Nadya
>
>No pageframs on form. The form is however very complicated. Im not sure Nick could work it out without all the supporting tables - that would be a nightmare to send him.
>
>I dont think I need to have a property with the name of the grid on it.
>
>I will delete GHL and re-add.
>
>BTH this only happens (if at all) when I release the form. Should I release the grid separately first?
>
>Thanks
>
>Colin