Hi Naveen

There's no easy way to code what you're looking for. A little while back I did some work for a client that required each trade (after the first) to use aspects of the previous trade as conditions for setting up each new trade. I can't disclose the actual code but it required a PREV-based latch to manage entries, pyramiding, exits and to monitor the previous trade as one of the conditions of entry. The code for tracking all trades in an indicator required 9 PREV functions, and the Long and Short TradeSim explorations each required 8 PREVs to faithfully implement all of the required trade conditions.

If you created the same system in the EST you'd still need to resort to PREV and/or several Simulation functions. The beauty of creating the system code as an indicator is that you can see exactly what's happening - this makes troubleshooting when things don't work properly so much easier. Trying to locate code problems in the EST or the Explorer without a visual aid is sometimes a real pain.

Your choices are to pay someone to create the necessary code, take the time to learn how and why a PREV latch works (which could be anywhere from a couple of weeks to several months) then do the work yourself, or change your system to something simpler. Actually there are a couple of other options and one would be to change to software to a package that made such projects easier (I have no suggestions on that score), or pay some like Wabbit to create a DLL for MetaStock and encapsulate the system.

As I said, there are no quick-fix answers.

Roy

Hi Naveen

Pyramiding is adding to existing trades, stacking one trade on top of another as each new entry signal is given.

Roy