View Full Version : Tradesim Database
ajellis
31st August 2003, 07:59 AM
I've just done a Tradesim exploration with a specific group of stocks. When I open the TS database for that exploration the trade database contains trades on an entirely different group of stocks.
Why?
David Samborsky
1st September 2003, 01:32 AM
Try deleting the trade database file in the c:\tradesimdata directory and then regenerate the trade database. Also please note the following extract from Document TB1.
RecordTrades function limitations
Due to the limitations of the Metastock external DLL interface there can be a problem when you try and rerun the same exploration with different portfolios particularly when the first security is different in each of the portfolios. The external Plug-In contains a number of variables which keep track of the database name along with the first security symbol. If you rerun a record trades exploration with a different portfolio, which has a different first security symbol name, the trade database file may not be reset or rewritten correctly. The symptoms of this problem are that the database may contain duplicate trades or exclude some trades. There are three ways around this problem:
1. Firstly, use different explorations with different trade database filenames when creating trade databases using the same trading system but with different portfolios ie “My Trades ASX100”, “My Trades ASX200” etc. The idea being that you always use the same portfolio list with the same trade database file and don't use the same trade database file name with different portfolio lists.
2. Run a different trade database exploration with a different trade database filename before you rerun the same trade database exploration.
3. Alternatively, delete the trade database (.trb) file before regenerating it. Trade database files are stored in the c:\tradesimdata directory. This will force the RecordTrades function to reset any internal variables and regenerate the trade database file correctly.
vBulletin® v3.8.6, Copyright ©2000-2012, Jelsoft Enterprises Ltd.