I just got 3/4 of the way through a query/export project that I was determined to do completely in webview - and as indicated, gave up 3/4 of the way and went back to dbv because it was too frustratingly slow. Oh and btw - when I was reviewing the query results - they were over the webview preview limit so the query told me to export it...

What really drove me to comment here: I use the description field to help number procedural steps (mostly annual functions/projects). It helps other staff follow along in the procedures - as the query names are not as intuitive to the order of processing. BUT then I found I couldn't sort by query description in webview - thought I was losing my mind. Also could not sort by 'last run date' to find the most recently used version. Back to dbv I went to get the project out on time.

It is amazing when you find out the little things that you take for granted are no longer available and you have to figure out a workaround or spend more research time ensuring you are using the correct query. I create query folders for major functions, but can't do this for every user's request - and it's not practical because I want users to see what's available before asking me to create something new...

Using and sorting by a query's description, last run, created date, etc. is way more useful than programmers think...

100% I cannot favourite ALL my queries, so I use description daily as a way to quickly navigate to batches of queries I need i a process. being able to sort by description makes my life so much easier. Not being able to do this in web view is stopping me from using it