FiveTech Software tech support forums

... 1 ] == "E". Converts any number formatted as string using either European notation or American notation, retaining the full precision of the decimal part. In almost all cases the function decides whether the format is European or not, by examining the number and position ...

... games ))) I could buy again a high performances laptop, +- 1500 and start using this. and finaly I saw a offer for this kind of machine : Dell Precision 7920 for around 2.900 euro (here some hardware like to much nVidia could be erased. Chassis Dell Precision 7920 CPU 2x Intel Xeon Gold 6130 ...

Hola joao saludos. Tambien intenté de esa manera, pero a nivel de menoria igual se trunca la precision decimal. En el caso que me ocupa necesito trabajar con numeros de 13 enteros y 8 decimales y no se puede almacenar un dato asi en memoria. Por lo menos yo no pude. Si ...

... Investigando y probando sobre el problema planteado sobre decimales, me encuentro que el mismo al parecer es heredado del viejo CLIPPER donde la precision con decimales se pierde cuando la variable numerica excede su maximo que segun lo leido es de 19 digitos. Pense en un principio que era problema ...

... datarow.prg: Mejorada la comprobación de fieldlen, fielddec en caso de los tipos adDouble y adSingle en ADO, dónde los atributos "Precision" y "NumericScale" no se especifican. En el caso de los campos numéricos en ADO, oField:Precision es equivalente a FIELDLEN() ...

... xbrowse.prg, datarow.prg: Improved ascertainment of fieldlen, fielddec in case of types adDouble and adSingle in ADO, where attributes Precision and NumericScale are left unspecified. * New function FW_ArrayAsRecordSet( [aArray], [aStruct] ) --> oAdoRecordSet Either aArray or aStruct ...

... using FWH It seems a Harbour bug using bcc7 64 bits in source\harbour\vm\itemapi.c /* converts a numeric to a string with optional width & precision. */ HB_BOOL hb_itemStrBuf( char * szResult, PHB_ITEM pNumber, int iSize, int iDec ) used from: char * hb_itemStr( PHB_ITEM pNumber, PHB_ITEM ...

... , probably this worked without changing the source. How can we see with the debugger the properties from oField as : numericscale , precision , ...... Frank Frank Demont

... my question might already have an obvious answer! For those of you that know, how does Harbour represent floats? Does it have any kind of limited-precision or arbitrary-precision decimal type? I need something either like the limited precision decimal type in C# or something with arbitrary precision ...

... Mr. Maurizio has stored the time values in Time format. Mr. Maurizio Excel internally stores Dates, DateTime values and Time values as double precision numbers and displays in the required format after conversion. So the time "08:50:00" is stored as a fraction of day, i.e., ( 8 * ...

... integer, short integer, double, CurDouble, RowVersion, or auto-increment field. It is possible to either overflow the value or lose decimal precision by using this function. If more precision is desired, use AdsGetDouble. When using this function to retrieve an auto-increment value, be sure ...

... into the Get. * New function cNumToStr( nVal ) --> cVal. \fwh\source\function\valtostr.prg. Converts a numeric value retaining full decimal precision and formatting as specified in FWNumFormat(). Example: FWNumFormat( "E", .t. ) n := 35/16 ? cNumToStr( n ), cValToChar( n ) --> ...

... width is provided for decimal fields. Fixed now Rowset data aStructure displays numeric column width following DBF convention and oRs:Field(x):Precision matches ADO convention. - NEW: oRs:Sort, oRs:ordSetFocus( c ), oRs:SetOrder( c ) can now use multiple columns. Eg: oRs:Sort := "AGE,HIREDATE ...

... will display the field as { "SALARY", "N", 9, 2 } i.e, following the DBF convention. oRs:Fields("salary"):Precision shows 8, matching ADO. oCn:ListColumns( ctable ) displays "Decimal(8,2)"

... on the table on a corresponding Memo field. All this works pretty well, except in 10% of the documents where Tesseract doesn't OCR with the needed precision and thus the "encounter" number can't be completely extracted. I've tried using the Tesseract learning tools with some success, ...