Avoid changed data immediately resorted by 'ORDER BY'
When an 'ORDER BY' clause exists, this sort order should remain until a new query is posted. Edited data should not be resorted immediately after posting a record - this behaviour interferes manual record changing (e.g. when copying a field value to the next record in the query result set).
This issue should be solved at least for temporary indexes with 'ORDER BY' by introducing an Option 'Fixed' for those indexes or, even better, making this the default behaviour (like MySQL etc.).
Similar problem with Skip and ISAM access - I have to store the next record and GoTo it.
This is where I have to store all of the record numbers and go to next record - not possible in SQL but is in ISAM.
This is a really good idea and would be very helpful.