FYI:

Alaska XBase++ seems to revaluate the deleted flag filter (set deleted on) 
when changing index orders (set order to).  This is not the same as Clipper 
or Foxpro 2.6a which do not change the current record when changing the 
current index order.

I have not tested, but suspect that Xbase++ may also revaluate the filter 
(set filter to) on changes to the current index order.

Rodd

hi,

> Alaska XBase++ seems to revaluate the deleted flag filter (set deleted on)

which Version of Xbase++ ?

> when changing index orders (set order to).  This is not the same as
Clipper
> or Foxpro 2.6a which do not change the current record when changing the
> current index order.

did you have !Deleted() in you Index-Key ?

in which situation did you have the problem ?

once i had something like this using TBrowse when deleting a record
and change Columne where every Columne had its own Index / Tag .
( have to look first for the next record and than delete / change columne )

 > I have not tested, but suspect that Xbase++ may also revaluate the filter
> (set filter to) on changes to the current index order.

not shure while using SCOPE instead of "Set Filter" ( is Scope a filter ? ),
but with Scope there ist a differenz ... it will jump to TopScope when set.

greetings by OHR
Jimmy

"AUGE_OHR" <AUGE_OHR*AT*CSI.COM> wrote in message 
news:hIbeRDhvFHA.2944@S15147418...
> hi,
>
>> Alaska XBase++ seems to revaluate the deleted flag filter (set deleted 
>> on)
>
> which Version of Xbase++ ?

v1.82 PRL 306
>
>> when changing index orders (set order to).  This is not the same as
> Clipper
>> or Foxpro 2.6a which do not change the current record when changing the
>> current index order.
>
> did you have !Deleted() in you Index-Key ?

No, index key is simple primary key (orderno).

>
> in which situation did you have the problem ?

OrdSetFocus() function call.

>
> once i had something like this using TBrowse when deleting a record
> and change Columne where every Columne had its own Index / Tag .
> ( have to look first for the next record and than delete / change 
> columne )
>
> > I have not tested, but suspect that Xbase++ may also revaluate the 
> > filter
>> (set filter to) on changes to the current index order.
>
> not shure while using SCOPE instead of "Set Filter" ( is Scope a filter 
> ? ),
> but with Scope there ist a differenz ... it will jump to TopScope when 
> set.

I have not used SCOPE as it is not in all xBase implementations the same.

I just did not expect the record to change due to a OrdSetFocus() call.  In 
my case, I returned to previous functionality by putting current record back 
(goto (OldRN)) after the call.

I post these differences so that future Clipper migrators can search the NG 
subject lines and gain immediate documentation to the differences.

Rodd

Rodd,

>Alaska XBase++ seems to revaluate the deleted flag filter (set deleted on) 
>when changing index orders (set order to). This is not the same as Clipper 
>or Foxpro 2.6a which do not change the current record when changing the 
>current index order.

I don't see this behavior here with either the DBFNTX nor the DBFCDX DBE. 
What DBE do you use? Can you post an example? Are you sure that you are not 
doing a DbSkip(0) (or something similar) after changing the Index?

-- Andreas

---                                                                      ---
  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
  415 Gute Street                     or: Andreas@DDPSoftware.com
  Owosso, MI 48867-4410               or: Andreas@Aerospace-History.net
  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
---                                                                      ---

ADSDBE with shared tables.  I checked the recno() in the debugger 
immediately prior to and after the OrdSetFocus() call.  The current record 
is deleted() and SET DELE ON is in effect.  I do understand that the record 
is filtered by the SET DELE, but was expecting to set the index order an 
move to the next record after deleting the current.

Rodd

"Andreas Gehrs-Pahl" <Andreas@DDPSoftware.com> wrote in message 
news:1k5w7muv6qapa$.8j82edq5kbqu.dlg@40tude.net...
> Rodd,
>
>>Alaska XBase++ seems to revaluate the deleted flag filter (set deleted on)
>>when changing index orders (set order to). This is not the same as Clipper
>>or Foxpro 2.6a which do not change the current record when changing the
>>current index order.
>
> I don't see this behavior here with either the DBFNTX nor the DBFCDX DBE.
> What DBE do you use? Can you post an example? Are you sure that you are 
> not
> doing a DbSkip(0) (or something similar) after changing the Index?
>
> -- Andreas
>
> ---                                                                      ---
>  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
>  415 Gute Street                     or: Andreas@DDPSoftware.com
>  Owosso, MI 48867-4410               or: Andreas@Aerospace-History.net
>  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
> ---                                                                      ---

Rodd,

>ADSDBE with shared tables.

This seems to be an ADSDBE-only issue, then. You might want to post this in 
the data-access (or even the bugreport) NG, but the best would be to send an 
email directly to <Support@Alaska-Software.com> -- if possibly with a small 
self-contained demo program, which reproduces the problem.

I checked the KB and even though a couple of the 92 ADSDBE-related PDRs 
sound vaguely similar to this issue, there is nothing about OrdSetFocus() 
affecting RecNo(). Neither DbDelete() nor OrdSetFocus() should EVER affect 
RecNo(), as this is Clipper-compatible behavior and the other Alaska DBEs 
adhere to this as expected!

Maybe this is a known and expected behavior for ADS (or the ADSDBE), but I 
would be surprised if it was, as this would require DBE-specific code for 
basic database operations like DbDelete() and OrdSetFocus(), which shouldn't 
be necessary!

-- Andreas

---                                                                      ---
  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
  415 Gute Street                     or: Andreas@DDPSoftware.com
  Owosso, MI 48867-4410               or: Andreas@Aerospace-History.net
  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
---                                                                      ---