FiveTech Software tech support forums

field->memo := hb_serialize( aVars )

...

aVars := hb_deserialize( field->memo )

no found METHOD Merge( cFileNew, aFields, aVars, cAlias ) CLASS TRichEdit5

... } ) si nAt es distinto de cero, entonces algún GET cambió Si las 50 variables pertenecen a un array, entonces puedes hacer: nAt = AScan( aVars, { | uValue, nIndex | oDlg:aControls[ nIndex ]:VarGet() != uValue } )

... Many thanks to Angel! * New: TRichEdit5 DATA lShowPageBreak METHOD Merge( cFileNew, aFields, aVars, cAlias ) METHOD HidePageBreak() // First test METHOD ImportExcel( nOp, nH ) METHOD ImportWord( nOp ) METHOD SaveAs( cFile ) METHOD SetNotModify() ...

... PRIVATE aSay :={"ID" ,"Nombre","Fecha"} PRIVATE aVars:={"cId","cName" ,"dDate"} MSGINFO(cId_User) IF !Empty(cId_User) MsgAlert(cId_User) GO TOP LOCATE FOR FIELD->USR_ID=cId_User ...

... cId:=SPACE(03),cName:=SPACE(100),dDate:=DTOC(DATE()),lActive:=.T. PRIVATE aSay :={"ID" ,"Nombre","Fecha"} PRIVATE aVars:={"cId","cName" ,"dDate"} IF !Empty(cId_User) MsgAlert(cId_User) GO TOP LOCATE FOR FIELD->USR_ID=cId_User cId ...

... PRIVATE aSay :={"ID" ,"Nombre","Fecha"} PRIVATE aVars:={"cId","cName" ,"dDate"} IF !Empty(cId_User) MsgAlert(cId_User) GO TOP LOCATE FOR FIELD->USR_ID=cId_User cId ...

... PRIVATE aSay :={"ID" ,"Nombre","Fecha"} PRIVATE aVars:={"cId","cName" ,"dDate"} IF !Empty(cId_User) MsgAlert(cId_User) GO TOP LOCATE FOR FIELD->USR_ID=cId_User cId ...

... source: \fwh\source\function\fwdecode.prg * Enhancement: MsgGet( cTitle, cText, aData ) Now MsgGet can handle arrays also. (a) Simplest usage: aVars := { Space(40), CToD(""), .f., 0.00 } lModified := MsgGet( "TEST", "Edit Values", aVars ) (b) Provide Prompts lModified ...

Thanks for the tips. I just found why the footers were missing. The first line displayed has character value " " in lieu of 0. So the AEval( oBrw1:aCols, { |o| o:cDataType := 'N' }, aVars[ 1 ] + 2 ) should resolve.

André,

Please change this line in your code:

REDEFINE COMBOBOX aGets[ 1 ] VAR aVars[ 1 ] ITEMS aArea ID 101 STYLE CBS_DROPDOWN OF oDlg

... me llega otra cosa diferente (&wq78Ç), algunos valores del peso pero otros no llegan y caracteres extraños. FUNCTION CapPes_Des(aAlias,aVars) LOCAL cCad cCad := "" // abre puerto IF !AbrePu_Des() RETURN (NIL) ENDIF f_info("Ahora ponga el articulo en la bascula") ...

... think I would want to risk using a hash table without knowing the answer to how collisions are handled. Also, I found that syntax used by Marizio (aVars) confusing. This normally represents an array and yet here it is holding a hash table which I have also seen refered to as an object in the literature. ...

So aVars := {=>} is an array of hashes? No, it is a single hash, that is essentially an array indexed by strings instead of numeric values. And can you also explain this syntax? aVars[FIELDNAME(nX)] := FieldGet(nX) I am ...

Enrico, No, it is the regular syntax required to initialize an empty hash (ie. similar to aVars := {} for arrays). So aVars := {=>} is an array of hashes? And can you also explain this syntax? aVars[FIELDNAME(nX)] := FieldGet(nX) I am guessing that it is creating ...