[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Creating a DataBase for ELA's



PureBytes Links

Trading Reference Links

I have done a  lot of work  with systems, and one thing that always bothers
me  is trying to remember  how the systems performed.  I would suggest
adding several other fields, such as exit strategy and performance on which
 underlying.  (Such as parabolic stop and 2 profit objectives.)  I have
found that any  system, such as breakout,  has vastly different results
based on the exit strategy.

I think your idea certainly has merit.

Regards,
Paul Weston

=========================================================

I was thinking of storing information on all my ELA's in an ACCESS
DataBase. The purpose is: (a) to have an analysis of the different types
of codes that I have, and (b) use this analysis to improve my
programming and trading ideas.

I planned a database structure :

1. Name of ELA
2. Type : ( Indicator / ShowMe / PaintBar / System / Function )
3. File Name in which the ELA is archived ( assuming there is a file
backup of the ELA )
4. Group Name: ( assuming the ELA belong's to a family of ELA's.
example: part of the ELA's for Hit and Run ...)
5. Underlying Logic: Trend / ContraTrend / Overbought Oversold /
Volatility / IntraDay / Time & Price / Swing Trade / Pattern
6. Keywords : 5 to 10 fields in which keywords associated with the ELA
could be entered. This would enable search later on.
7. Functions Required: List of functions used by the ELA
8. Include systems required
9. DLL's required
( I suppose functions,include sys and dlls list has to be stored in a
child database ).
10. Actual Code: could be in a text field, or could point to a text file
where the code is stored.

Please tell me if (a) the creation and maintaining of such a  database
is a good idea at all. (b) Please suggest improvements in the database.

If I do develop the database and a user interface for it, I would be
happy to share it with list memebers.

Thanks,

Sudarshan Sukhani




<