You shouldn't have to do anything to associate the UltraCalcManager with the grid when you add it to the form at design-time. If you're adding it in code, you can assign the CalcManager property of the grid to the instance of the UltraCalcManager that you've created.
As for setting properties, if the column structure is the same as when you bind the data, you can set the various conditions whenever you want, though generally the ValueBasedAppearance logic makes the most sense at design-time, since otherwise you might be better off using the InitializeRow event (though in the case of FormulaConditions, this may not necessarily be true).
-Matt
Does this have to happen on the Initialize Layout event?
Can I set these properties before I bind the data?
Also After adding the UltraCalcManager, how do I associate it w/ the grid?
Thank you.
And UltraCalcManager it was. Never heard of it, never used it before...
Thx!
I'm not sure what the problem could be then, as your code worked for me perfectly (after the formula modifications). I'm also assuming that you have an UltraCalcManager on the form, since a FormulaCondition will not work without it (and may explain why you didn't have the problem that I mentioned regarding the performance and formula compilation errors). If you do have an UltraCalcManager on the form already, you should submit a small sample to Developer Support so that they can look into it.
"columnDescription" is indeed the same as '__grid.DisplayLayout.Bands[0].Columns["Description"]'
I have changed the formulas but it has no effect.
Even if I use some dummy formula like "1 != 2" the appearance doesn't change.
Using some simple OperatorConditions works fine, however,that's not what i need here...