FiveTech Software tech support forums

... - 1      WITH OBJECT oRs:Fields( n )         AAdd( aTypes, { :Name, :Value, :Type, cAdoType( :Type ), ;               :DefinedSize, :Precision, :NumericScale } )      END   next   XBROWSER aTypes TITLE "ADO FIELD TYPES" SETUP ;      oBrw:cHeaders := ...

Whatever DefinedSize we specify while creating the table (via sql or adox), when the table is read using ADO, the field object is showing oField:DefinedSize as 255 only

... i , cName, nType, nLen      ocol:Name := cName      ocol:Type := nType      IF aStruct[i][ 2 ] == "C"         ocol:DefinedSize := nLen      ENDIF      oTable:Columns:Append( ocol )   NEXTfwlog i , Var2char(oCat), Var2char(oTable), Var2char(oCat:Tables), ...

... from each field object of the RecordSet. The issue with ADO for Excel is, whatever length of char we specify it always returns 255. oField:DefinedSize. Please try this:   n := 0   aFields := {}   do while n < oRs:Fields:Count()    ...

That is the issue with ADO with Excel.
Whatever length you specify while creating the table, that is ignored.
ADO RecordSet field object always shows oField:DefinedSize as 255.

... son exportados correctamente en todos los casos. - Los campos "ADO" de tipo "adVarChar" o "adVarWChar" con "DefinedSize -1" no eran mostrados. Ahora, son mostrados como campos "memo". - Hashs de navegación: si el primer valor es numérico, los ...

... are not exported unless oBrw:lCellExcelWise is set to .t. Now exported correctly in all cases. - Ado fields of type adVarChar or adVarWChar with DefinedSize -1 were not being displayed. Now, they are displayed as memo fields. - Browsing Hash: If the first value is numeric, logical and date values ...

... and save, FWH implementation refreshes current record only after save, using ReSync() method. This should make a difference in performance. 3) DefinedSize logitud campo, ........... Impleneted in the latest version: DefinedSize, ActualSize, Precision, NumericScale, OriginalValue Proposed to ...

... trabaja perfecto 2) oRcs:Update() uso oRcs:Save() trabaja bien, sin embargo cada tabla debe tener un indice principal 3) DefinedSize logitud campo Precision longitud campo numerico NumericScale cantidad de decimales Uso oRcs:FieldLen(oRcs:FieldPos(cCampo)) oRcs:FieldDec(oRcs:FieldPos(cCampo)) ...

... myself to read with GET's. First I test for the type. I use oQry:fields("naam'):type = 129 for charachters Then I use oQry:Fields('naam'):DefinedSize to get the field length I use this for all datatypes

Antonio,

oRs:Fields( n ):DefinedSize

Anyhow Mr. Rao is the real expert on ADO/SQL

... nField - 1 ):Precision ELSE nLen := ADO_GETFIELDSIZE( ADO_GETFIELDTYPE( oRecordSet:Fields( nField - 1 ):Type ), oRecordSet:Fields( nField - 1 ):DefinedSize ) ENDIF /* Un campo mayor de 1024 lo consideramos un campo memo */ uInfo := iif( nLen > 1024, 10, nLen ) CASE nInfoType == DBS_DEC ADO_FIELDINFO( ...

... n - 1 ):Type ) aField[ UR_FI_TYPEEXT ] := 0 aField[ UR_FI_LEN ] := ADO_GETFIELDSIZE( aField[ UR_FI_TYPE ], oRecordSet:Fields( n - 1 ):DefinedSize ) aField[ UR_FI_DEC ] := 0 #ifdef UR_FI_FLAGS aField[ UR_FI_FLAGS ] := 0 #endif #ifdef UR_FI_STEP aField[ UR_FI_STEP ] := 0 #endif UR_SUPER_ADDFIELD( ...

... reason. Good practice is to use VARCHAR(nwidth) fields. Also it is good practice to store Trimmed values. We can not store strings larger than the DefinedSize. (This raises an error). When we read we get the string of the same length as we have stored. It is possible to store padded strings. We ...

... Ado Type of the field as numeric You can find all ado field types here http://www.w3schools.com/asp/ado_datatypes.asp For character fields: oField:DefinedSize --> Field length For Numeric fields of type Decimal and Number: oField:Precision --> Length oField:NumericScale --> number of decimals ...