Sorry, no, I have not studied it. The default is .T., try the opposite. During developement, you can usually see the result by issuing _screen.themes=.F.

>Hi Tore,
>
>>Check the themes property!
>
>OK, have done, but are you aware if there is any correlation between a grid's backcolor/forecolor and its container.
>
>Thanks,
>
>
>>
>>>Hi,
>>>
>>>I have a custom grid that can be set to display the normal background colour of white when the cursor source is inherently read-only, ie., when the cursor source is from a non-updateable SQLPT cursor. In these cases, without my modification, the grid displays the following backcolor '13160660', the same shade of grey as the form. In my custom code, if the read-only cursor source is empty of records, I still want to display the usual read-only colour ie., '13160660'. When the the read-only cursor source has records, then the refresh code in the grid sets backcolor to White. All pretty straightforward <s>.
>>>
>>>Here's the rub. If the application runs in XP, then hard coding these colour may look very silly indeed if the user is using Themes. Does anyone know the best approach to ensure that my ReadOnly/Not-ReadOnly backcolor settings will be commensurate with the current XP theme setting - eg., I could use the form's backcolor as the grid's read-only backcolor.
>>>
>>>Any tips would be appreciated.
>>>
>>>Thanks,