No...no...Nick, the automated script won't delete the ticker filename that is stored in certain AB directories, instead, the script would utilize AB (will automatically open AB) and call the import function (OLE automation) and refresh the current data with new data, this way, any other information won't be lost (studies). Layout directory won't be touched either. This full refresh function would probably be done once a week (can be adjusted) and daily refresh would only be getting daily data instead of full refresh. Eventually when AB is closed (all neccessary process is done - AB Scans or whatever), another utility/small app. would check if there is any files that need to be deleted by comparing the full list of tickers (most likely in a plain text file) with files that are located in AB database. This utility might be optional though, since keeping old AB files won't probably hurt too much. (These days hard- drive cost is getting cheaper and cheaper, and the size is getting bigger and bigger, and AB database for each ticker is miniscule even if it had 10-year eod data).
Gary. --- In [EMAIL PROTECTED], Nick Busigin <[EMAIL PROTECTED]> wrote: > > On Thu, 12 Apr 2007, Gary wrote: > > > This is a good start, I will start this little project soon then... > > My goal would be: the data would be just like the way I am doing now, > > all the scans are done and the database would have all eod data from > > yesterday when I look at charts. I just need to go through a short > > list of stocks as the results of automated scans. > > I don't really care how many stocks get deleted/added each day > > either, if we download and refresh the database everyday then I guess > > we don't need to worry about this problem. > > There is only one problem with the approach of essentially re- creating > the database as I do periodically with the data that Jim so generously > provides - and that is any studies I have created are lost, as I believe > these are stored in the same files as the data is. It would be nice to > have a migration tool to copy them over from the old database files. > Alternatively, it probably wouldn't be too big a deal to write a utility > program that compares the old database files with the new ones and just > adds/deletes the changes to the existing database rather than doing a > complete change-over. A project for when I have a little more time. > > Nick > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =-= > Help fight the war against Spam; > Erase all addresses before forwarding any item of email. > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =-= >
