|
PureBytes Links
Trading Reference Links
|
Jim,
The examples are covering exclusively the Access implementation.
Then :
" export to a text file in the appropriate format. Import the data
via the Downloader "
IOW, each time there is a split eg, you end up having to perform
an update in both Access and Metastock databases = there is NO
integration !
Come on, you have hundreds of splits and symbol modifications in
a year. Do you think it's a good solution ?
This discussion is however good at providing Equis guidelines about
what their software is primiraly missing.
I mean, there should be a Downloader function applying
Quote.com-like delisting/symchange/splits files to the specified
directory tree. And not the way it is updating splits currently,
obviously.
As there should be a way to those schedule Downloader operations
(via macros, scripts ?)
It seems we are far from the original topic ;-)
Br. Alain.
______________________________________
At 14:22 25/09/97 -0700, Jim Michael wrote:
>On Thu, 25 Sep 1997, Alain Jossart wrote:
>> If this is the case, how would you integrate the Access and Metastock
>> databases (splits, delisting, symbol modification, etc) ?
>
>Let's look at your 3 example problems:
>
>Splits
>
>Find a web site where split info is published. Use a Perl script to
>retrieve the info and parse to an input file for Access. In Access create
>a table with fields Ticker, SplitDate, Ratio. Create a macro which imports
>the split data file into the Splits table and runs an update query which
>applies the split ratio to the data prior to the split date for each
>ticker having a split.
>
>Delisting
>
>You might want to keep a table of delisted stocks and the date they were
>delisted. Use referential integrity rules to tie your related tables
>together, then delete the records for the delisted stocks from the master
>table, taking related records with them.
>
>Ticker and exchange changes
>
>A good Master table is one containing the Ticker, CompanyName, Exchange.
>If you have your referential integrity established as above (cascade
>update, cascade delete) then making a change to this table will change
>the entries in the related tables.
>
>Add any other data maintenance items you need (how about volume
>adjustment after changing data sources?) and use a query to create
>the table with the same fields as your input file for MS, then export to
>a text file in the appropriate format. Import the data via the Downloader.
>
>Hope this helps.
>
>Cheers,
>
>Jim
>
>
|