FiveTech Support Forums

Hello

Xbrowse does not behave the same way with the autosort clause when browsing a dbf or an array

I explain , with dbf if we click on the header of the column, the sort is done and then the display will start on the same record as it was but sorted on that particular column. Bseek is issued automatically with autosort

In case of arrays , when clicking on the header of a column , the autosort is performed and we are positioned on the top of the array and this is a bad behaviour. seekonarray is not invoked in this case

Any idea how to correct this ?

Thanks for the help,

Richard

Fwh 10.10 but the problem is the same with fwh 11.01

In case of arrays , when clicking on the header of a column , the autosort is performed and we are positioned on the top of the array and this is a bad behaviour.

      ::oBrw:nArrayAt   := AScan( ::oBrw:aArrayData, uSave )

      ::oBrw:nArrayAt   := AScan( ::oBrw:aArrayData, { |a| a == uSave } )

Mr Rao

Tested , the fix is correct.

Many thanks for your quick reply,

Best regards

Richard

Richard , Nages :

Using Customer.dbf , index on FIELD->Last (column2 )

1) Ordering a dbf (using an index) and ordering a array (column) will not give the same results for equal fields when we look ar the recordnumber.
For 'Bink' we have 125 , 152 ,176 , 382 there is a subkey record number

In the array (first try ) : 152 , 176 ,382 , 125
second : 382 , 125 , 176 , 152
AT RANDOM !!!

2) When in the arraysort 'Bink' is searched to reset the browse , one from the 4 'Binks' is found (the first one in the ordered array)
This gives total wrong results when is clicked on a column as 'Married' (only .F. or .T.) . When the array is reset the first occurance from usave (.F. or .T.) is found , it has nothing to do with 'Bink" ! We have to combine this column with another to make it unique

Only with a subkey we can improve xbrowse . The results would be much better with a index on LAST + FIRST , but equal names (last+first) are still there . Search in 'Bink Gregory' gives one from the two.

For using subkeys with xbrowse see : viewtopic.php?f=3&t=21153
Saving uSave and restoring it must be changed in MySetArray

Both problems can be solved with adding a column record number (or numbering the array)

In the DBF the indexexpression seems to be LAST + STR(RECNO()) , so in the array :

oBrw:aCols[2]:bOrder := {|a|TRIM(a[2])+STR(RECNO(),6)}

I will adapt the example in viewtopic.php?f=3&t=21153 to have a working example

Frank

This key is unique . It would also be possible to save (usave) to the recnumber (sortarray)

I

Saving uSave and restoring it must be changed in MySetArray

Nages ,

I am using FWH 8.10 and tested :

1 ) Select BRINK (4 names) , Change between A and D several times , select item changes (between the for names)

2) click on married , no brinks more selected.

Sorry when it works now as expected

Frank

Mr. Frank

There have been a lot of improvements to fwh and xbrowse over these years. I have seen the code you posted in the other post.

All that would not be needed now.

nageswaragunupudi wrote:Mr. Frank

There have been a lot of improvements to fwh and xbrowse over these years. I have seen the code you posted in the other post.

All that would not be needed now.