FiveTech Software tech support forums

... .OR. lSingleSelect cHtml += '<th data-field="st" data-checkbox="true"></th>' ENDIF FOR n := 1 TO Len(hCols) aField := HB_HPairAt( hCols, n ) cField := aField[1] hDef := aField[2] cHtml += '<th data-field="' + cField + '" ' cHtml += 'data-width="' ...

I made function bCampo2( aFields, nFor,oDbf) return oDbf:fieldWBlock(aField[nFor] ) and seem run , it's wrong ? >If you do not want a simple, straightforward and reliable approach and you insist on complicating your programs it is ...

Daniel Is there an working example for update or insert into MySQL database with TDolphin Afield: = {"id", "sound", "maried", "total", "description", "date_maried"} Avalue: = {"12345", "c: \ ring.wav". ...

... of FWH or Harbour or xHarbour. The alternatives in hbusrdd.ch are (one of wich shoul work) : a) #define UR_FI_SIZE 5 comment in ado_open // aField[ UR_FI_FLAGS ] := 0 // xHarbour expecs this field // aField[ UR_FI_STEP ] := 0 // xHarbour expecs this field b) #define UR_FI_SIZE 7 add in hbusrrd.ch ...

Hello, In hbusrrdd.ch, there is: #define UR_FI_SIZE 5 Yes, before posting I comment out with no luck: // aField[ UR_FI_FLAGS ] := 0 // xHarbour expecs this field // aField[ UR_FI_STEP ] := 0 // xHarbour expecs this field Antonio, maybe as Antonio´s developing a great efford ...

Lucas,

You re right Ill apply your changes.

Comment these and check what is the UR_FI_SIZE in hbusrdd.ch

aField[ UR_FI_FLAGS ] := 0 // xHarbour expecs this field
aField[ UR_FI_STEP ] := 0 // xHarbour expecs this field

I think Harbour ony accepts 5 ele.

... you are using DBFS with ADS: STATIC FUNCTION ADO_OPEN( nWA, aOpenInfo )   LOCAL aWAData := USRRDD_AREADATA( nWA )   LOCAL cName, aField, oError, nResult   LOCAL oRecordSet, nTotalFields, n   LOCAL nCountIndexes // see below   /* When there is no ALIAS we will create new one using ...

Antonio,

In ADO_OPEN we load all fieldinfo UR_SUPER_ADDFIELD( nWA, aField ).

How can we get back after the information save there?

Antonio,

FieldLen and FieldSize return nil

I've tested in the adorrd before UR_SUPER_ADDFIELD( nWA, aField ) and the values are correct.

What can we do?

AHF wrote:Antonio,

I checked usrrdd.c from xHarbour and it expects aField[ UR_FI_FLAGS ] aField[ UR_FI_STEP ] that I now send := 0.


Its ok now

Will keep you posted

Very good!

Antonio,

I checked usrrdd.c from xHarbour and it expects aField[ UR_FI_FLAGS ] aField[ UR_FI_STEP ] that I now send := 0.


Its ok now

Will keep you posted

Antonio,

Passed array its corrected.This is the print out:

aField[ UR_FI_NAME ] = NRENCOMEND
aField[ UR_FI_TYPE ] = 1
aField[ UR_FI_TYPEEXT ] = 0
aField[ UR_FI_LEN ] = 10
aField[ UR_FI_DEC ] = 0


It seems the error its not here.

Antonio, Yes and I checked with : msginfo(str(HB_Decode( aField[ DBS_TYPE ], "C", HB_FT_STRING, "L", HB_FT_LOGICAL, "M", HB_FT_MEMO, "D", HB_FT_DATE, "N", IIF( aField[ DBS_DEC ] > 0, HB_FT_DOUBLE, ...

Antonio, I checked with msginfo() and the values in aField passed to UR_SUPER_ADDFIELD( nWA, aField ) are: nWa = workarea number aField[ UR_FI_NAME ] := "name of field" aField[ UR_FI_TYPE ] := one of "C","L","D","N","M" ...

Antonio, All that we can do here is to double check that we have properly filled aField before calling that function. I doubt there is an error like this in the Harbour RDD engine, so I guess we are suplying wrong values to aField If everything is ok, we may need ...