FiveTech Software tech support forums

Mr leandro If the RecSet has atleast one Row at the beginning, later even if all the rows are deleted also, the browse works well. But if we start with an empty RecordSet ( like an empty array ), the browse fails while trying to compute the datawidths. Try writing code ...

... some change in behavior that you want all your database to inherit, you an add it to the TXData class. For example, lets say you want to reuse deleted records. You can add the code to do that in TXData, then TMeter and any other database class that you have created will automatically inherit ...

... the filter expressions. If not, the RDD optimizes the filter either patially or not at all depending on the availability of filters. When we SET DELETED ON, the RDD's require index on the expression 'DELETED()' also to optimize. Then, if we set filter like 'FLD1 = 'SOMETHING' .AND. FLD2 = 'SOMETHING' ...

On large tables if you find the filter to make the program slow, you can always create one more index tag 'INDEX ON DELETED() TAG DELETED'

Can you explain it because i don't understand it

Thank you
A.S.K

There is another way if you are using DBFCDX only. Create the index on normal way. But when you open the table, set filter to !deleted(). OrdKeyCount() and OrdKeyNo() respect filters and scopes. So you get only 2 keys. On large tables if you find the filter to make the program slow, you ...

Create index with for !deleted() condition.

Yes but WHY? If i use set deleted on WHY does it counts the records? This is a BIG problem because i cannot move within my indexed records. Any solution?

Thank you
A.S.K

Please create the table, index and close.
Reopen and then do the test. Both RDDs count deleted records.

Try this #include "fivewin.ch" request DBFcdx FUNCTION MAIN() SET DELETED On DBCREATE( "TMPTEST", { { "TEST", "C", 10, 0 } } ) USE TMPTEST via "DBFcdx" INDEX ON FIELD -> test ...

... each row.. Rick oBRW:nClrText := ; { || SelColor( oRs:Fields("code"):Value,oRs:Fields("DEL_CODE"):Value,oRs:Fields("EXPIR_DATE"):Value,oRs:Fields("DELETED"):Value,"F" ) } oBRW:nClrPane := ; { || SelColor( oRs:Fields("code"):Value,oRs:Fields("DEL_CODE"):Value,oRs:Fields("EXPIR_DATE"):Value,oRs:Fields("DELETED"):Value,"B" ...

... we do notice great sluggishness with large tables, To find a solution we need to understand the behaviour of these functions. We normally use SET DELETED ON. We are not interested in seeing the deleted records but interested in dealing with the live records only. The functions AdsGetRecordCount ...

James Bott wrote:Enrico,

It seems that the logical-length can only change when a record is added, deleted, or the filter or scope is changed.

Or when another user adds or deletes a record...

EMG

Enrico, It seems that the logical-length can only change when a record is added, deleted, or the filter or scope is changed. So, if there was a new var, nLogicLen, then it could be corrected only when any of the above things changed, and thus bLogicLen would only ...

Construye el indice con la claúsula FOR ! TuAlias->( Deleted() )

Prueba con

SET DELETED ON | OFF