Hello,
Could some of the vets offer some advice on using search? I'm still finding it awkward and unintuitive even after reading the help file again. Here are a couple of questions but any additional advice on using search would be appreciated.
1) How do I edit an item shown in the search list? In Ecco Pro search result items can be edited like any other. In my omnibox search results, selecting an item selects the whole row but you can't edit any fields.
2) How do I go to the item in its grid? If I click on the grid in the "Shown In" column, it takes me to the grid but not to the specific item in the grid. To find the item, I have to do another search inside the grid. This is the biggest problem I'm having with integrating search into doing actual work. It seems like clicking on the grid link should take you to the specific item in that grid. Surely there's a way to do that.
Wayne
Comments
In v84, I've added this:
In v84, I've added this:
Maybe does it work for a super small DB, but probably not for Dbs used for research (with a lot of text and many classification fields).
To me it always seemed that to be really useful, the "fast search/quick find" window should integrate what's already in the "advanced find" dialog (as advanced options) and... allow easy editing, marking, etc. like any other normal grids.
I suggest to alwaysOffer to hoist the results in that grid. (maybe except for search/scratch)2- Since it's "advanced", allow some of the same cool options the quick find/fast mode presents. E.g. Show items in new search grid (instead of recycling the same one), Show items in current grid, Show marked items, Show favorites, Show orphans, etc.)
3- Allow filtering the text results not only by one field, but by several fields, maybe using somekind of field pane (properties pane?)/drop down, with each field being fillable/checkable
4- Still in the "advanced find" dialog : I think the "Source view" expression could be replaced by "filter by..." or "Show...", which would probably be less esoteric.
Maybe does it work for a super small DB, but probably not for Dbs used for research (with a lot of text and many classification fields).
Maybe does it work for a super small DB, but probably not for Dbs used for research (with a lot of text and many classification fields).