-When doing a find/replace operation based on any, or some, options available (such as date, check number, and classification) it will find the records and display them as "selected all". I see no reason the program should ASSUME I selected all. I didn't!
-After de-selecting the record(s) I don't want to change, I find that if I forgot to add fields to change, like "tag" or "cleared status" the program RE-SELECTS all previously found records! I find this to be outrageous and unexpected (especially to novices) program behavior. Search results can be numerous and the user can be faced with choosing between hand editing records, or just throwing the whole session away, starting over with the previous session or backup.
NOT COOL!
-Furthermore, it will NOT effect changes unless Cleared Status is the first elected field to change. Nor cool either. IMHO
.~~~~~~~~~~~~~~~~
Another thing IMHO that is "uncool" (but may be unavailable with the architecture of the dataset which I read somewhere is based on the legacy Ashton-Tate dBase(series)) is being unable to change fields encountered in split transactions. For example if I have a group of records I want to change the tags and/or categories, or I want the memos to read a certain way, it won't change them. Why not?.
~~~~~~~~~~~~~~~~
Why can't text strings be changed within a field? I intended to write "help for a friend" in the memo field but missed the "r' and ended up with "help for a fiend". OK, I guess, for Gomez and Morticia Addams, but not I.
~~~~~~~~~~~~~~~~.
Lastly the notes are a wonderful addenda but they should be editable, sortable, and searchable too...like the memo field. IMHO.
My thanks to all of you!
