FiveTech Support Forums

Hello,

Best technique for this kind of checks (If a certain condition, then color....)

oBrw[6]:T4:bClrStd := { || if (at( oRs:t1_4 , 'AZKSVTXF' ) > 0 , { CLR_BLACK,CLR_HRED } , { CLR_BLACK,CLR_WHITE } ) }

In a online system (oRs) do we check by the fieldnames of the database of do you prefer to check the values from the Xbrowse.
(I have no sample for this now)

Check by database, will look into the online system, and that is maybe no the ideal situation.

We advise you to use XBrowse names as far as possible. This helps us to write code portable across different data sources.

Marc

Be careful in your code block that your oRs:Field or NOT Null .. put another in line If( oRs:Eof, ,your code )

Rick Lipkin

Sorry Rick, I don't folow what you mean ? Could you explace a little more ?

oBrw[6]:T4:bClrStd := { || if (at( oRs:t1_4 , 'AZKSVTXF' ) > 0 , { CLR_BLACK,CLR_HRED } , { CLR_BLACK,CLR_WHITE } ) }

You are right ! Have to think of this.

In the sample above, it was the idea to get rid of the oRs calls, but use the Xbrowse field instead, because it is a simple call to color a column in the browse.

oBrw:oCol:Value is safer and simpler. This never fails.

If the browse is something like:

@ r,c XBROWSE ..... COLUMNS "FIRST", "LAST", ......... HEADERS "FirstName", "LastName", .......

Then
condition like oBrw:FirstName:Value = <something> is better than oRs:First value or oRs:Fields( "first" ):Value.

Reasons:
1. oBrw:Col:Value never errors out
2. This works whether you are browsing DBF, ADO recordset or MYSQL or any other datasource.

XBrowse and TDatarow are specifically made to enable programmer to write portable code.
If you still refer to or use oRs or cAlias you have decided not to take advantage the power of xbrowse.

Thanks.

And no, I surely prefer also the Xbrowse code. I just had not the code yet... Now I have