FiveTech Software tech support forums

Thank you Mr. Rao I did what you suggested, but the error persists Eg: COLUMNS "NAME", "QTY", "RATE", "QTY*RATE" ; Taking your example, it does not perform the operation. the columns "NAME", "QTY", "RATE" ...

Not 7-8 FIELD NAME OF 7 - FIELD NAME OF 8 Eg: COLUMNS "NAME", "QTY", "RATE", "QTY*RATE" ; HEADERS "ClientName", "Quantity", "Price", "Amount" Also it is not a good practice to provide ...

... what are you trying to do but having problems/confusion. For this example =============== COLUMNS "ITEM","UPPER(NAME)","QTY","PRICE","QTY * PRICE" ;HEADERS "Item", "Name", "Quantity", "Rate", "Amount" ...

... ) --> Salary field is incremented and written to table and returns the value ITEMS->( FW_DBLOOKUP( 101, "ITEMCODE", { || FIELD->QTY -= nOldQty } ) ITEMS->( FW_DBLOOKUP( 103, "ITEMCODE", { || FIELD->QRY += nNewQty } ) STATES->( FW_DBLOOKUP( 10, 0, "FIELD->NAME" ...

... la lógica para evaluación de expresiones utilizadas mientras se explora ADO y MySQL. Cuando las columnas se definen como "NAME","QTY","QTY*RATE", etc., las expresiones como "QTY*RATE" son internamente traducidas como: oRs:Fields( "QTY" ):Value ...

... * XBrowse: - Enhanced logic for evaluation of expressions used while browing ADO and MySql. When columns are defined as "NAME","QTY","QTY*RATE", etc., expressions like "QTY*RATE" are internally translated as: oRs:Fields( "QTY" ):Value * oRs:Fields( ...

oBrw:QtyOrd:bOnChange := { | oCol | oBrw:extPrice:VarPut( oCol:Cost * oCol:QtyOrd ) }       COLUMNS "Itemno","Descrip","Cost","Qtyord","ExtPrice";  ...

... también puede ser una matriz de nombres de campo/expresiones. - Es posible especificar un encabezado diferente a la expresión especificando "QTY * PRICE AS AMOUNT". El valor de QTY * PRICE se exportará con el encabezado "AMOUNT". - Se formatean los números de texto y decimales. ...

... - cFieldList can also be an array of field names/expressions. - It is possible to sepcify header other than the expression by specifying "QTY * PRICE AS AMOUNT". Value of QTY * PRICE will be exported with the heading "AMOUNT". - Text and decimal numbers are formatted. As ...

... value="] + cCommodity + ["></th>] ) put( [ <th>Quantity</th>] ) put( [ <th><input name="qty" type="text" size="30" value="] + cQty + ["></th>] ) put( [ </tr>] ) put( [ <tr>] ) put( ...

... , ; STR( qtedim->len, 5 ) , ; STR( qtedim->wid, 5 ) , ; STR( qtedim->hgt, 5 ) , ; STR( qtedim->lbs, 9, 2 ) ; ID 5000 ; HEADERS "Qty", "Pkg", "Commodity", "(L)", "(W)", "(H)", "LBS" ; FIELDSIZES 75 , 100 , 200 , ...

... bom2.itemidc itemidc,cversion,goods2.descrip descrip,goods2.size size,unit.unit unit,substring(bom2.mem,1,25) mem,bom2.qty/bom2.qtydevisor*(1+ifnull(bom2.scraprate,0)/100)+bom2.fixscrap qty,bom1.version version,bom2.position position"; +" from "+ctable1+" ...

... ) --> Salary field is incremented and written to table and returns the value ITEMS->( FW_DBLOOKUP( 101, "ITEMCODE", { || FIELD->QTY -= nOldQty } ) ITEMS->( FW_DBLOOKUP( 103, "ITEMCODE", { || FIELD->QRY += nNewQty } ) STATES->( FW_DBLOOKUP( 10, 0, "FIELD->NAME" ...

... be used for storing binary data like images. b) To create a computed column ( virtual ) specify the field name as formula like: { "amount = qty * price", 'N', 12, 2 }, ... This column will be created as amount DECIMAL( 12, 2 ) AS ( qty * price ), c) To spcify primary key add one more ...

... etc. Second database is STOCK.dbf having field ICODE,WH_ID,STOCK, & set relation on ICODE and data records of Stock.dbf as below ICODE WH_ID QTY ITEM1 W1 10 ITEM1 W2 5 ITEM1 W3 5 How to browse ARTICLE.DBF and show Qty of WH_ID="W1" .and. WH_ID="W2" only. XBROWSE FIELD ...