Hi Kevin A "date flter" is probably my most used indicator for system testing. It allows me the flexibility to set start and end test dates that are not specifically tied to the amount or dates of data actually loaded. What I suggest you do is add a simple "time filter" indicator to your system entry and exit rules along the lines of the code below. The default Input() values for the indicator should be set as required so that the Fml()function can be used to filter entry signals and if necessary force exit signals. {Time Filter} {Roy Larsen, 10/7/2011} Sh:=Input("Time Filter, Start Hour",0,23,7); Sm:=Input("Start Minute",0,59,30); Eh:=Input("End Hour" ,0,23,14); Em:=Input("End Minute" ,0,59,30); Start:=Minute()>=Sm AND Hour()=Sh OR Hour()>Sh; End:=Em>Minute() AND Hour()=Eh OR Eh>Hour(); Start AND End OR Start*Alert(Start=0,2); On the other hand you could probably dispense with the filter as an indicator and insert the code directly into your system's entries and exits. Start:=Minute()>=30 AND Hour()=7 OR Hour()>7; End:=30>Minute() AND Hour()=14 OR 14>Hour(); Filter:=Start AND End; Filter; The "OR Start*Alert(Start=0,2)" component of the indicator's output line forces a TRUE spike at the beginning of the Start variable going TRUE if the Start signal is inadvertently set to occur later than the End signal. Hope this helps. Roy