Diff. between FIND 'QueryName' and DISPLAY 'queryName'

BLOMASKY

So, every now and then I re-read the rules reference to see what shiny new features have been added, I see the following:

FIND 'Open accounts' this action will run a query named ‘Open accounts’.

How is this different from DISPLAY 'Open accounts'???

Bruce

yahya

FIND is followed with an action that being a rule/process based on the FIND query.
DISPLAY will just show the results of the query.

Jaymer

Or...

FIND executes the named query, and puts the results in context

BLOMASKY

ah ha! so FIND 'Query Name' does not display the results of the query. it just FINDS the records, puts them in Context with NO UI?

Bruce

PointsWell

BLOMASKY wrote
ah ha! so FIND 'Query Name' does not display the results of the query. it just FINDS the records, puts them in Context with NO UI?

Bruce

And DISPLAY query generally has to be the last item of your process if you are embedding the query into your VP/tab, otherwise it will appear in a pop up window.

BLOMASKY

I do understand why there are many queries with WHERE clauses, but the way I develop, the ONLY time a query has a WHERE clause is when I have had a form prompting for filters prior to running the query. And since my queries always have an ORDER BY, I never think to use one instead of a FIND.

Not right or wrong, but compared to other tools, you can adjust your aware programming style to what works best for you.

Bruce

PointsWell

BLOMASKY wrote
, I never think to use one instead of a FIND.

If you only use that FIND once then it has no impact, but if you use that same FIND more than once then you reduce your code redundancy and remove the risk of updating the FIND in one place and forgetting to update the other by using a query

tford

One small practical aspect .. now that Queries can be organized by Category in the Congif Tool, I try to group the ones that are only used in a FIND in category / categories by themselves.