Hi Glenn,

I now see what your problem is. We can use "GetRow()" but there's no "GetColumnName()". Sorry for the advice on "@col" without actually trying.

 So here's what I came up with:

You have a global function which receives a rownumber (long) and a columnName (string).
Let's say it's called "gf_from_dw(long al_row, string as_col)"
In your column's attributes for background color, you initially set a dummy same expression for all columns:

gf_from_dw(getrow(), "[not_set_yet]").

Then somewhere, maybe in the constructor of the dw control,
you "loop through all of your columns", 
do a describe of the current expression ...
and replace the "[not_set_yet]" with the real column name...

To save time explaining, I've added Sample.zip.

Ignore almost everything on it, it was used for something else, just look at the button that says "none".

You'd still have to add some functionality which loops through all columns and not only the fixed "compute_1" as it does right now.

 regards,

hope it gives you an idea

Wow, almost time to "get up" :)

This code works for me demo:

// Validation expression for column = myName
f_check( GetRow( ), Long( Describe("myName.ID")) )

GLOBAL FUNCTION f_check(long row, long column) return Boolean
// Demo - always accept any value
MessageBox(string(row), string(column)
return true

Notice, GetRow( ) in DW expressions returns the row that calls the function.

Describe("<columnname>.ID") returns column's number as a string, so I convert to LONG to pass as numeric value.

HOWEVER,
I would consider writing scripts on the DataWindow control - or NVOs having direct access to the DataWindow control (like "services" attached to the DW control). There you have much more freedom in access to the complete API of the DataWindow control - and access to the DataWindow object including its API inside the control.

HTH /Michael