|
PureBytes Links
Trading Reference Links
|
At 15:09 23/02/99 -0500, Sean W. Smith wrote:
>
>
>> -----Original Message-----
>> From: owner-metastock@xxxxxxxxxxxxx
>> [mailto:owner-metastock@xxxxxxxxxxxxx]On Behalf Of Alain JOSSART
>> Sent: Tuesday, February 23, 1999 4:55 AM
>> To: metastock@xxxxxxxxxxxxx; metastock@xxxxxxxxxxxxx
>> Subject: RE: file structure and data handling
>>
>>
>>
>> What you is said is true excepted the inability to browse multiple
>> metastock dirs is not a characteristic of MS format, this is a limitation
>> of the Metastock package IMHO.
>>
>
>
>True this wouldn't be a problem without 2000 limit.
I'm afraid it would anyway with multi-market unlimited directories.
>> Some good points however (could read what made it a standard) :
>> * very easy creation/deletion of markets
>
>??? What do you mean by this
Just that adding futures, removing mutual funds or copying a group of
securities to create a "test market" is quite simple with the
Metastock/Computrac data organization.
>> * support of custom symbols
>
>??? same question...
Easy example - creation of custom index.
>> * free utility to maintain database, import ASCII data
>
>Where???
Reuters/Equis free Downloader. People can get free CSV quote files for many
world markets and use The Downloader to maintain Metastock files.
Most data vendors of these countries will also support the data format.
Again, The Downloader can then be used for data maintenance.
>> * 255 sec/dir data structure technical documentation has been
>> available for years, 2000 sec/dir is a simple (&dirty) extension
>> (if one omit the access control mechanisms)
>
>Yep
>
>> * supported # data records allows for long term historical studies
>
>most formats have this.
Dunno. This one will let you cover 30 years and even 1929 :) I like to know
that a structure is "unlimited enough" that I do not need to remember it
has a limit.
>> * ever read a message about MS database crash ?
>
>YEP sure have. I have had there data get corrupted by the downloader when I
>was first using dial data/
I guess there were some occurences, was just mentioning the number of crash
reports is really low for such a widespread stock database format. It is
slow and kind of horrible for sure, but I really appreciate the no crash/no
hang performance.
>
>
>>
>> More negative points :
>> * No separate split storage (really hate that)
>>
>> -- Alain
>> ________________________________________________________
>> At 09:42 22/02/99 -0500, Sean W. Smith wrote:
>> >poor file handling.
>> >
>> >here are the issues I think characterize MS format versus some its
>> >competition.
>> >
>> >2,000 security per directory limitation.
>> >
>> >inability to browse charts across multiple metastock dirs as Advanced Get
>> >allows
>> >
>> >Slow to Moderate Performance
>> >
>> >Poor utilization of space using MS format compared to others.
>> >
>> >Sean
>> >
>> >
>> >> -----Original Message-----
>> >> From: owner-metastock@xxxxxxxxxxxxx
>> >> [mailto:owner-metastock@xxxxxxxxxxxxx]On Behalf Of Hlouschek
>> >> Sent: Monday, February 22, 1999 6:03 AM
>> >> To: metastock@xxxxxxxxxxxxx
>> >> Cc: Lionel Issen
>> >> Subject: Re: file structure and data handling
>> >>
>> >>
>> >> Lionel and Gail Issen wrote:
>> >>
>> >> >Glen:
>> >> >
>> >> >Equis strengths are in good documentation and prior to V6.0, very good
>> >> >technical support.
>> >> >Equis' weaknesses are a poor file structure and data handling and an
>> >> >unwillingness to do a complete update on their program.
>> >> >
>> >>
>> >> Lionel,
>> >>
>> >> can you explain a little more in depth what you miss regarding
>> poor file
>> >> structure
>> >> and data handling. I think these are relevant points.
>> >>
>> >> - Stefan
>> >>
>> >>
>> >>
>> >
>>
>
|