FiveTech Software tech support forums

... Nueva opción PORT en SET ADO DEFAULT DATABASE ... ADO_ORDINFO ordwildseek implementado Soporte de órdenes múltiples con nuevo SET: SET ADODBF MULTIBAG INDICE LIST A {{"INDEX NAME", {TAGORDER 1 "," TAGORDER2 "}}} Esto permite que el soporte de archivos de índices ...

... New features: New option PORT in SET ADO DEFAULT DATABASE ... ADO_ORDINFO ordwildseek implemented Multibag orders support with new SET: SET ADODBF MULTIBAG INDEX LIST TO { { "INDEX NAME", {TAGORDER 1","TAGORDER2"} } } This allows multibag index file support exactly ...

... TO "EMPRE01" SERVER TO "localhost" ENGINE TO "MYSQL" USER TO "root" PASSWORD TO "1234" /* SET ADODBF TABLES INDEX LIST TO { ; {"EMPRESA",{"EMPRESA","NUMEMP_000"} }, {"APUNTES" ,{"APUIND01","AP_OBRA+DTOS(AP_FECHA)"}} ...

New build adordd ver 1.0 at https://github.com/AHFERREIRA/adordd.git New: 1) SET ADODBF INDEX LIST FIELDTYPE NUMBER TO {{ "Table",{ "numfiled", nlen },{"numfield", nLen } } } adordd need a precise indication of the len of numeric fields ...

New build adordd ver 1.0 at https://github.com/AHFERREIRA/adordd.git New: 1) SET ADODBF INDEX LIST FIELDTYPE NUMBER TO {{ "Table",{ "numfiled", nlen },{"numfield", nLen } } } adordd need a precise indication of the len of numeric fields ...

... DBGOTO was giving error if the record was not within INDEX with UDF or condition. Changes: hb_AdoRddFile( cFile ) Check for index file in the adodbf index list... and support for Sqlite, Firebird, Oracle.

... DBGOTO was giving error if the record was not within INDEX with UDF or condition. Changes: hb_AdoRddFile( cFile ) Check for index file in the adodbf index list... and support for Sqlite, Firebird, Oracle.

... USE cTable SET INDEX TO index1,index2,index3 Order focus should be index1. If SET AUTOPEN ON the order focus will be on the first index in the SET ADODBF.. You should only use INDEX ON for temporary indexes as permanent ones should be indicated on SET ADODBF INDEX... If you use INDEX ON... TO cFile ...

... indexfiles. As in ADORDD no files exist i must use before INDEX ON... (in a clipper app only once to produce the indexfile) or the command SET ADODBF TABLES INDEX LIST TO .... If i use this ADODBF TABLES INDEX LIST TO .... then the order from the indexes always like this array. The SET INDEX ...

... If INDEX ON is after it will be added after. If autopen off index on will be added first if you not did explicitly set index to the index in ADODBF INDEX. If you found other behavior this is not the standard clipper its a bug!

Antonio, not a bug!
I have tested ADODBF INDEX ... and INDEX ON... at same time. The OrdList begins always with the indizes defined in ADODBF INDEX ... This is very important to know!

Gunther,

Im glad to know that it suites you.

...that indexes with ADODBF INDEX ... are in ordernumber < indexes created with INDEX ON... and both can used the same time

I dont understand what you mean.Is it a bug?

Antonio, i use MSSQL. I have explored in the meantime the rdd. All is ok. And i found out, that indexes with ADODBF INDEX ... are in ordernumber < indexes created with INDEX ON... and both can used the same time. Indexes without UDF are really extreme in speed! Some indexes ...

Gunther, Any valid clipper expression must work. If not something is wrong with adordd. ADODBF INDEX ... is only for indexes that are used by the app and are created only once. All indexes created (normally temporary) during app run time should not be place there. adordd ...

Antonio, a suggestion:
In ADOSHOWERROR() should also the database an the actual table displayed!

And a question:
Code like

Code: Select all  Expand view

INDEX ON TESTADISC->REDATUM TO TMP

are functioning? Maybe this command can fill the SET ADODBF TABLES INDEX LIST TO...