FiveTech Software tech support forums

... y n está dentro del tamaño y si n es '0' devuelve oItem:cPromt y en caso contrario devuelve 'nil'. Si n está dentro del rango, oItem[ n ] := newValue también funciona. * Función XEval( uVar, p1, p2, ... ) mejorada. Ahora uVar también puede ser un nombre de función que termine con "()". ...

... is an array and n is withing the size and if n is '0' returns oItem:cPromt and else returns 'nil' If n is within the range, oItem[ n ] := newValue works too. * Enhanced XEval( uVar, p1, p2, ... ) Now uVar can also be function name ending with "()". If the named function is linked, ...

... write a right name of a field Since you are already using a database object, instead of this: oDbf:FieldGet( cField ) oDbf:FieldPut( cField, <newvalue> ) You can just do: oDBF:ID oDBF:Name Where ID and NAME are fieldnames. Then you can do: msgInfo( oDBF:ID ) To put data into a field of ...

... write a right name of a field Since you are already using a database object, instead of this: oDbf:FieldGet( cField ) oDbf:FieldPut( cField, <newvalue> ) You can just do: oDBF:ID oDBF:Name Where ID and NAME are fieldnames. Then you can do: msgInfo( oDBF:ID ) To put data into a field of ...

... > 0, this cell width extends to that many cells on the right side. Also if some cells in an array contain codeblocks, these are evaluated with newvalue, array, row, col as parameters and result is displayed in this cell. https://imagizer.imageshack.com/img924/6257/GbKrGh.gif ...

aModifed := oRs:ModiCols()xbrowser aModified  If you want to modify values of some fields and then save, oRs:<fieldname> := <newvalue> and then oRs:Save() is okay. Even you can offer edit of records this way, but we recommend using Datarow, which is a lot safer and feature ...

... are using xbrowse, you need not write reclocks, recunlocks, etc. XBrowse takes care of everything automatically. Just use oBrw:oCol:VarPut( <newvalue> ) If the <newvalue> is different from the existing value, xbrowse writes the value to the dbf, takes care of all locking issues and ...

... CheckSum(<cString>)->nCheckSum Chr(<nCode>)->cChar ClearBit(<nInteger>|<cHex>,[<nBitPos,...>])->nNewValue ClearEol([<nRow>],[<nCol>],[<xColor>],[<xChar>])->cNull ClearSlow(<nDelay>,[<nTop>],[<nLeft>],[<nBottom>],[<nRight>],[<xChar>])->cNull ...

... maybe there is also a new method in Xbrowse that handle this better ? If any change in a cell are done, then I want to save (Fieldname, oldvalue, newvalue) So I also need the Older data of the cell, and the new data. Any samples that uses this technique ?

... problem is with creating TDataRow once and using it always. TDataRow works only for one record. Actually you can directly use oRs:FieldName := <newvalue>, oRs:Save() Modify the code like this @ nTop,nLeft+nMove BTNBMP aBtn2[i] OF oFld:aDialogs[ 2 ] SIZE 28, 15 NOBORDER PROMPT ...

...  dbSelectArea(cOldSele)return nil  When PVENAUS is edited, this column is automatically re-totaled. oBrw:PVenta:VarPut( <newvalue> ) changes the value of PVENTA and also automatically re-totals PVENTA column. Need not call MakeTotals() again at runtime.

... this code may run into several lines and again in each line the laborious coding of "oRs:Fields( "<name>" ):Value := <newvalue>" Instead, I suggest considering the following single line approach: oRs:Update( { "FIRST", "LAST", "AGE", ...

oBrw:oTreeItem:Cargo[ 1 ] := <newvalue>
oBrw:RefreshCurrent()

... scanning the Directory with Wildcard to detect the last used Numer ? scanning for : _Image1_*.jpg aDir := directory('.\Images\_Image1_*.jpg') NewValue := Len( aDir ) + 1 Existing Files : _Image1_1.jpg _Image1_2.jpg _Image1_3.jpg _Image1_4.jpg the next new Filname must be => _Image1_5.jpg ...

... __XHARBOUR GLOBAL Var1 # else STATIC Var1 # endif In prg1 we provide a function # ifndef __XHARBOUR FUNCTION Var1() RETURN var1 Or FUNCTION Var1(NewValue) IF PCOUNT()>0 Var1 := NewValue END RETURN var1 # endif In other modules # ifdef __XHARBOUR GLOBAL EXTERNAL Var1 # else # xtranslate var1=>var1() ...