HbDbu, ntx multitag

[Luigi Ferraris]

Hi Pritpal,
using HbDbu with ntx multitag I see this "little" problem.

Multitag is set like this
         ::ordCondSet( "!DELETED()", {|| !DELETED()}, .T. )
         ::ordCreate( ::indexName(), "byCode", "prgcodeid", {|| FIELD->prgcodeid }, .F. )

         ::ordCondSet( "DELETED()", {|| DELETED()}, .T. )
         ::ordCreate( ::indexName(), "beDeleted", "RECNO()", {|| RECNO() }, .F. )
        
On current dbf there are 3 records and one of them is deleted.

ScreenShot001: I open dbf without any index. You can see all records. Ok
ScreenShot002: I have open ntx. You can see NOT deleted records. Ok
ScreenShot003: I will select the new tag. Ok
ScreenShot004: This is what I can see. Wrong: this record is not deleted
ScreenShot005: I have pressed button "GoTop". I can see the right record. Ok

IMHO: when tag is changed, a "GoTop" must be performed by default else wrong data are still shown.

BR
Luigi Ferraris

[Pritpal Bedi]

Hi Luigi

On current dbf there are 3 records and one of them is deleted.

ScreenShot001: I open dbf without any index. You can see all records. Ok
ScreenShot002: I have open ntx. You can see NOT deleted records. Ok
ScreenShot003: I will select the new tag. Ok
ScreenShot004: This is what I can see. Wrong: this record is not deleted
ScreenShot005: I have pressed button "GoTop". I can see the right record. Ok

IMHO: when tag is changed, a "GoTop" must be performed by default else wrong data are still shown.

A good catch, thanks, will fix shortly.

Pritpal Bedi

a student of software analysis & concepts 

[Luigi Ferraris]

Hi Pritpal,

> A good catch, thanks, will fix shortly.

Today I have used HbDbu, with multitag NTX index, but this problem is already present.

Best regards
Luigi