Hey Mike & Mike,
Thanks for your assistance and all with this issue. Unfortunately, I still don't think we're quite there yet.
loRep.Sections("D"

.ReportObjects(1).ForeColor = IIF(CONDITION = .T.,RGB(255,0,0),RGB(255,255,255))
The thing about the above statement is that, while it is valid and seems like it'd do the trick, it doesn't.
The data I’m using is being pulled from a SQL Server to the CR via OLEDB. I set that up with a statement such as:
loReport.Database.AddOLEDBSource("Provider=SQLO-LEDB;SERVER=testsql;DATABASE=sales;UID=sa;PWD=xxx","YTDSales"
By doing that, and correct me if I'm wrong, the data goes straight from the SQL Server to the CR engine and VFP never sees it, right? And therefore that solution won't work, cause the data at that point isn't even read by VFP, right? And so it has to be a CR formula, not VFP, right, cause the CR engine needs to “look” at the data, not VFP, right?
In the CR IDE we can easily enter a formula for a report object to determine the forecolor it should be printed in. What I need to do is just that, but thru the CR activex control. The .ReportObjects(1).Forecolor property expects only an RGB value, a formula can't be entered there, right? I tried things like:
.ReportObjects(3).Forecolor = "If CurrentFieldValue > 1000 Then Red Else Black"
but with that all I got was the invalid parameter error generated by the CR COM object. There's gotta be somewhere to store a formula like that, right? Any ideas?
Once again, your assistance here is greatly appreciated!!!
Dan