Jim Dean![]() Sage ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3433 Joined: 3/13/2006 Location: L'ville, GA ![]() | Four possible methods, with most reliable/sure listed first: Best is to modify the System so that the signal fires one day later - can do for OLang systems but can't do for canned systems. My normal approach to stuff like this. Another possibility that you can try is set up the Trade Plan with a Condition attached to the MOC Entry order ... that is, when the Signal fires, the first Step is initiated ... if the Condition is Nbar=1, then in theory that should delay the execution of that step for one extra day. HOWEVER, I've found many problems in the past when trying to apply Conditions to Entry orders, so be sure to check this one out carefully. Hopefully it will work. Another possibility is to attempt to write the Condition as a Stop in OLang ... again, my prior testing using OLang conditions for entries has had a poor success rate ... OT needs some tuning up in this area. Hopefully the canned N-bar approach above will work for you. FINALLY ... maybe there is some way using the Confirm block with the very same System enabled, but fiddling with the Before or After inputs, to delay the trade that one day. But there is apparently sometimes a problem with the "After" inputs, so again, check carefullyl. |