You could try to filter something like:

a1:=SAR(0.02,0.2);
a2:=Cross(C,a1);
a2

Hi Zombie The reason for your exploration failure is most likely because you're running the Explorer with "Minimum Records" rather than setting a number of 50 or more. From memory the SAR() requires 16 or 17 bars of data before it will deliver a real result, otherwise you'll just get N/A. I don't think that number of bars needed varies with the parameter settings but, as I say, loading 50 bars or more will get rid of the reason for most N/A results. Roy

Hi Zombie I tested John's code in colummn A on the US S&P 500 for the 7th of December and got the following results. N/A on all securities when loading 16 bars or less. 15 hits when loading 17 bars. 30 hits when moving up from 95 up to 100 bars loaded. 30 hits on all passes with more than 100 bars (I went as high as 5000 bars) I ran the test again with John's code in the filter and got exactly the same results. These results confirm that with "Load Minimum Records" only N/A results can be expected. Some but probably not all events will be detected with 17 or more bars loaded. It would be wise to load 250 or more bars to be sure of getting all hits - more bars loaded improves the accuracy of this particular test. Apart from underestimating the number of bars required to pick up all Cross events I think my original comments pretty much covered the most likely cause of your problem. The only other thing that I can think of is that you modified John's code in some way so that it no longer perfermed the function you required of it. Identical code in both the Indicator Builder and the Explorer will produce identical results if the same number of bars are loaded. The only thing different is the way the results are presented. Make sure that the Explorer is set to the same periodicity as the charts you're using for making any comparison. Roy