FiveTech Support Forums

Antonio,

I guess, at ADO_LOCATE(), in aWAData[ WA_SCOPEINFO ][ UR_SI_CFOR ] for the find, all before -> should be ignored, with substr o sttoken.

Thank you.

That info about readonly or not is in aWAData, but I don´t know it´s structure.

lucasdebeltran wrote:Antonio,

I guess, at ADO_LOCATE(), in aWAData[ WA_SCOPEINFO ][ UR_SI_CFOR ] for the find, all before -> should be ignored, with substr o sttoken.

Thank you.

DBI_ISREADONLY --> lIsReadOnly (READONLY)

See also: command USE. The return value is .T. (true) when a database file is open in READONLY mode in the current work area.

i) You have ANNOUNCE ADORDD twice on top of it.



ii) Also, at ADO_OPEN() you have to comment out:

/*
aOpenInfo[ UR_OI_NAME ] += ".dbf"

hb_adoSetTable( aOpenInfo[ UR_OI_NAME ] )
hb_adoSetEngine( "")
hb_adoSetServer( "")
hb_adoSetQuery( )
hb_adoSetUser( "")
hb_adoSetPassword( "" )
*/


iii) And:

// aWAData[ WA_TABLENAME ] := SUBSTR(CFILENOPATH(aWAData[ WA_TABLENAME ] ),1,LEN(CFILENOPATH(aWAData[ WA_TABLENAME ] ))-4)



iv) Browses requiere mandatory at ADO_OPEN() :

oRecordSet:CursorLocation := adUseClient //its slower but has avntages such always bookmaks
oRecordSet:LockType := adLockOptimistic

Ok Ill do that.

Antonio, Lucas,

:find wiht more than one field diferent or the same mentioned on the expression its not possible in ADO.

Thus Im going to filter .
Then calling continue will skip through the filter set.

Is this ok for the general use?

Yes, that´s the only possible way in ADO.

Also, please don´t forget to open indexes automatically.

Antonio L., I think we might wait some days, as adordd.prg need some extra testing.

But, indeed, it´s going to be superb.

lucasdebeltran wrote:Yes, that´s the only possible way in ADO.

Also, please don´t forget to open indexes automatically.

Antonio L., I think we might wait some days, as adordd.prg need some extra testing.

But, indeed, it´s going to be superb.

New version adordd https://github.com/AHFERREIRA/adordd.git

Relations working. (I hope)

I think we can even relate tables in 2 different connections ex one MySql another Oracle. Didnt tried yet.

Find works.
If only one field mentioned in the expression calls Find if not Filter
When CONTINUE is called and when is filter skip +1

Seeks working.
Please remember that seeks are truly selects. Thus after a seek the "table" select is left only with the seek results.
If we do another seek or a while seek expression true there isnt any problem however if we try to go to a record saved before the seek will get error.

There is a new aWAData[WA_ISITSUBSET] to control this but I didnt yet find how to know if the default set is needed. For a ex a goto out of the set?
This seems to be a huge problem.

Antonio do you have any idea over the seek problem?

lucasdebeltran wrote:Hello,

In DBFCDX, there is not need to call SET INDEX TO..., indexes are opened automatically. Just:

Code (fw): Select all Collapse

 USE ( cMyPath + "CUSTOMER.DBF" )           NEW  ALIAS "CUST"
   CUST->(OrdSetFocus("CUST1"))

Nothing more.

Antonio do you have any idea over the seek problem?

      
         INDEX ON FIELD->NOMBRE                TAG CLIENTES1   FOR !Deleted()
         INDEX ON FIELD->CODIGO                TAG CLIENTES2   FOR !Deleted()
         INDEX ON FIELD->NIF                   TAG CLIENTES3   FOR !Deleted()
         DbCloseAll()

STRUCTURAL BAGs
A structural index is no more than a BAG whose particularity have the same name as the table.

What we gain from this? Is that opening the table to which it is associated, also opens automatically
command economy. It is usually created automatically with:

USE MyDatabase New
INDEX ON TAG TO FILE NAME = TABLE´S NAME
....


Also:


SET AUTOPEN
Toggles automatic opening of a structural index file.
Syntax
SET AUTOPEN ON | off | (<lOnOff>)

Arguments
ON | off | (<lOnOff>)
The option toggles if a structural index file is automatically opened with the USE command. With ON or .T. (true), an index file is automatically opened. OFF or .F. (false) switch this mode off. Description
Some replaceable database drivers support automatic opening of index files with the USE command when the index file has the same file name as the database file (without extension). An example is the DBFCDX driver. SET AUTOPEN toggles this behavior.
When SET AUTOPEN is set to ON, which is the default, the USE command automatically opens an index file having the same name as the database file and the file extension returned from OrdBagExt().
Note: if an index file is automatically opened, a controlling index is not activated. The default index order is zero, i.e. records are accessible in physical order in the work area. To select a controlling index, call OrdSetFocus() or use SET AUTORDER for a default controlling index.
Info