What can I do from within my fex to provoke a nocache result? When I run the below fex, I toggle between the current and previous versions of the fex rather then re-executing (and getting new results from) the fex. I do not want to depend on the users altering the cache setting in their browsers.

Here's the Final Code:

-*************************************************************
-* SORT_TEST: Douglas Lee & Preeti Sahi @ Ford Motor Company *
-* Demo report to show functionality of alternating sorting  *
-*************************************************************
-RUN
-DEFAULT &RANDOM_RPT = '&TOD.EVAL';
-DEFAULT &SORT_ORDER = 'HIGHEST' ;
-SET &SORT_ORDER = IF &SORT_ORDER EQ 'HIGHEST' THEN 'LOWEST' ELSE 'HIGHEST';
-SET &SORT_MRKR  = IF &SORT_ORDER EQ 'HIGHEST'
- THEN '<span style="font-family: Webdings; font-size=22px; color: #00bb66;">5</span>'
- ELSE '<span style="font-family: Webdings; font-size=22px; color: #ff0000;">6</span>' ;
-SET &MODEL_TITLE = 'Model [ ' | &SORT_MRKR | ' ' | &SORT_ORDER | ' ]';
TABLE FILE CAR
SUM DEALER_COST AS 'D Cost'
BY &SORT_ORDER.EVAL 'CAR.CARREC.MODEL' AS '&MODEL_TITLE'
HEADING
"The Car file with selectable sort order on MODEL"
"Executed on &DATE at &TOD (Last ran at &RANDOM_RPT)"
ON TABLE SET PAGE OFF
ON TABLE NOTOTAL
ON TABLE SET STYLE *
     UNITS=IN, SQUEEZE=ON, ORIENTATION=PORTRAIT,$
TYPE=REPORT, GRID=OFF, FONT='ARIAL', SIZE=10, COLOR='NAVY',$
TYPE=TITLE, COLUMN=N1, FOCEXEC=app/sort_test(SORT_ORDER='&SORT_ORDER' RANDOM_RPT='&TOD'),$
ENDSTYLE
END

Don't concern yourself as to the "Why does he want to do this?" ... I just do... It is possible, right? After all "We can do that in WebFOCUS!"
BTW: I hope you like the cool up/down arrows...

This message has been edited. Last edited by: Doug,

If I understand, just add in a random number in the drilldown.

FOCEXEC=app/sort_test(SORT_IN='&SORT_ORDER' RND=&TOD),

Good one Waz... Actually, that's what IB said... But, Why do I need to do that now... I remember not needing that, although it does work.

Have you heard about 'EXPIRE_REPORTS"? To ensure that a report is re-executed, set EXPIRE_REPORTS to 1.

It may depend on where the fex is run from and what URL is generated for the drilldown.

My suggestion is to play it safe and add in the random number.

As for EXPIRE_REPORTS, no I had not heard of it.

Interesting....

I think that I would not like it, as it will cause more requested to be sent to the WF server for processing. By adding in the random number your fex decides if it needs to refresh, and if the user wants to, then they can press F5.

quote:

EXPIRE_REPORTS

Is new to (I think) 7.6.10... I'm closing this post...