🚀 go-pugleaf

macq@miguel.llnl.gov (Don MacQueen) writes:
>The latest on my list of things Claris broke when they went from Filemaker II
>to Filemaker Pro:

>A database is sorted.  You find a subset of the records.  The found subset is
>NOT, I repeat NOT NOT NOT sorted in the original order.  This is the most G.D
>stupid imbecilic asinine design decision I have run across in a long time.
>Because it means that EVERY time I find a subset I have to re-sort.  And then
>when I go back to the original entire set, I have to re-sort AGAIN.

Thank you for your comments.  While the behavior you describe may be annoying
to you, it is the same way that FileMaker II behaved.  It was not changed in
FileMaker Pro.  While we would have liked to change it so that the records
would remain sorted after the find,  we were somewhat limited by the
existing architecture of FileMaker II.  In order for us to retain the sort
order after every find, we would need to automatically perform a sort
after every find operation.  This would slow down finding dramatically
and would be annoying to some users.  Hopefully in the future we will be
able to change the architecture to make this work the way you would like.

>Claris are you listening?  USE YOUR BRAINS.
>-- 
>flame off. **&%#%!&!!_)!%!@!_)(*^!&!&*!@&&(*&!@(*@!^)
>--------------------
>Don MacQueen
>macq@miguel.llnl.gov
>--------------------

I understand your frustration, and I assure you that we are listening to
your comments.

Brian
-- 
Internet: skip@claris.com                 AppleLink: SCHIPPER1