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

Re: Error in metastock file format (1900 instead of 2000)



PureBytes Links

Trading Reference Links

----- Original Message ----- 
From: "Henry Amand"
To: "metastock list" <metastock@xxxxxxxxxxxxx>
Sent: vrijdag 10 maart 2000 17:07
Subject: Re: Error in metastock file format (1900 instead of 2000)


> Thanks to all who replied. My suspisions seem to have been right and
> my datavendor is doing something wrong.
> 
> a few more questions (and some clarification) about the error (if i may :-)
> 
> >   To Test the here by you send set of {incomplete} (NDK) MSK files for the
> >   AEX:
> 
> That is all my datavendor puts on the harddisk.

1). The way files were send "was incomplete" for my DLv5.2 to read the
      set 'instantly', eg in one(1) single Open action. See also 3).
  
 > >   -first : I had to add {to your set} my own EMASTER file for the Aex
> 
> If i open the files with the downloader that file is (automaticaly) created.

2). See 3).
 
> >   -than: I had to rename your
> >                -f1.dat and f1.dop files to F1.dat and F1.dop
> >                -the master.dat file to MASTER
> 
> If i open the directory with the downloader the master.dat file is being
> (automaticaly) renamed to MASTER.DAT.

3). Your master.dat or MASTER.DAT (or MASTER.dat) are not recognized
valid (security) MSK files. They were tho in previous program versions.
The current EOD program version (both MSK 6.52 and DL 6.52) here requires
a MASTER and EMASTER files (without the .dat extension) and Fxx.dat file(s)
(with the .dat extension) to be present, eg for minimum, and a "plain" .dat file
will be seen by program as any other common (known or unkown) file type
and as such NOT as a security file.
 
> >   -than in the DL could finaly view the AEX {see AEX.gif}
> 
> I can view the files without having to do all that. but the downloader
> is doing a lot automaticaly for me. (at the end it ofcourse is all the same.
> something is wrong)

This "being able to view the files" suprises me, unless you are using an older program
version {or if Equis changed policies (again), a brand new version}.
Creation of the EMASTER (note again without the.dat extension) is likely "automaticaly"
done so, since the previous program version's "Maximum per Folder held contents"
limit of 255 securities/folder (using Fxx.dat file format), was EXTENDED to the somehow
unlimitted quantity/folder (using the Fxx.mwd file format) available in current program version.
(MASTER + EXTENDED = EMASTER and mwd = metastock windows data).
 
> >   --------------------------------------------------------
> >   Tets-results: {see AEX.gif and NewAEX.gif)
> >   {note: in this I am using here different Country Settings than yours, eg
> >    US vs Dutch}
> 
> How important is that ? that also is a date issue but i can not imagine
> that it couses my problem. I believe by the way that i also tested with
> country settings to US.

For the WYSIWYG screen display contents naturaly a very important issue, but for exchanging
the security's data with other programs can be VITAL. Eg Select all data, click Copy and
than Paste Clipboards contents to for instance Excel, and the xls-sheet will give "different values"
than your file's original (visable) contents. Convert to Excel file will also give "different values", eg
now (maybe) the correct values.
 
============================
BeursMedia, another Dutch dataprovider, too is suffering from their own very stupid
{Windows incompatible} programming bugs, i.e.
the "Translation-of-foreign-language-values-battle", occurring when their Retriever conversion
program interpret the divisor
"comma" (in US=thousands, in Dutch=decimal)
for the
"period"  (in US=decimal, in Dutch=thousands).

For example using their program, a Close of 21,68 will then be converted as follows:
   -Original download or ASCII txt file value      = 21,68 {correct+rounded would be 22}
   -Windows default {OS=Dutch version}value = 21,68
Now in Windows Control Panel using Dutch Country Settings:
       -in DL Converted to MSK data file value   = 21.6800
       -in DL Copied + in EXCEL Pasted value = 21.680,00
       -in DL WYSIWYG displayed value             = 216,8000 {4 positions from right=separator}
Now in Windows Control Panel using US Country Settings: {note: still in a Dutch Windows OS} 
       -in DL Converted to data file value            = 21.6800
       -in DL Copied + in EXCEL Pasted value = 21.6800
       -in DL WYSIWYG displayed value             = 21,6800 {4 positions from right=separator}

For your NDK's Translation-battle's date bug query, note as well that in the Windows Control Panel,
the Country Settings for Dates can be altered  -from the Windows default-  into:
-to US's values YYYYMMDD or
-to US's values MMDDYYYY (MM/DD/YYYY) or
-to EUR's values DDMMYYYY (DD/MM/YYYY) or
-to EUR's values DD-MM-YYYY
and that using a shorter writing version in the set of letters for the period, eg D or Y or YY,
can have  -a very strong negative impact on / to giving different results in-  other programs as well !!!
But see my previous mail's "conclusion" and Opinion+Advice below for better advice.
====================================================== 

> >   1) The file's dates+data contents are correct
> >        and that's too why your Charts (dates) are also in agreement
> >   2) Except that the "First date:"-field in the NDK's master.dat file is
> >       incorrect
> >       to test I have copied and pasted only the dates+data to a newly
> >       created NewAEX file
> >      and the DL now shows the correct "First date:" values
> 
> Strangely enough, also the last date settings are incorrect. In the
> screenshot you can see a correct last date but if you for
> instance choose Adjust first date from the
> tools menu you will also see an incorrect last date.

This is indeed 'strange', and yet again not so strange(your NDK's master.dat).
Again see Opinion+Advice below. 

> > ---------------------------------------------------------
> > Conclusion:
> > NDK is not creating correct master files. Either "live" with these short
> >  comings or choose for the NDK's daily ASCII data files to be
> >  send and than Convert these.
> 
> I hope to convince them they are doing something wrong so they can correct
> the "problem". This daily data option from my data vendor is a very nice
> one.

Opinion +Advice
Please, let ONLY the DL create proper data files.
There aren't that many programs around that can create good solid MSK Data Files.
In fact, the only one that I know of in capable to do so is................the DL.
(Not surprisingly, if you know that Equis isn't giving away for free its MSK Data File
information and too, that many programmers have bugger all knowledge
of the MSK progarm(s) + MSK files full stop).

The by your NDK (and BeursMedia's Retriever) created master.dat files are
bugged clones: "Cheap imitations".
So, do not use their CdRom and/or from Download sessions created master.dat files,
but like Lionel also correctly suggested, build from scratch.

E.g. in the DL program AND in ANOTHER FOLDER (so as you will NOT be using
the CORRUPTED master.dat file created by NDK/BeursMedia) create a new AEX security.
Then only Copy the Data sheet's contents to this newly created AEX security
and please Delete the NDK's/BeursMedia's corrupted AEX security. 
Do these ACTIONS for all of your NDK's/BeursMedia's securitiues.

Then start to daily update-ing to these newly created security files. I am also sure
that now the correct MASTER and EMASTER file versions (note without the .dat extension)
will also keep their original layout and correct (First date:) values and that files will not be
overwritten by these "cheap" messing about conversion program's master.dat files
(NDK/BeursMedia).

Tip
Look at the previous send Tips in how to Create a List of tickers(Symbol List) or see the Help,
to automaticaly create ALL of your Tickers securities in one(1) action.
Then Convert  -from MSK to ASCII txt-   all of your "corrupted' NDK/BeursMedia securities,
and back Convert from these ASCII txt files to MSK, eg to the newly created securites.
You will have this fixed within an hour to a couple of hours depending on the amount
of your master file corrupted securities.
You will also then have bypassed these "malfunctioning" programs mentioned above, and
are now set for live with these   -now correct-   functioning pleasurous program files.
Than forget about their confusing Help??Desks.

> > That is too, how I receive them from FIBBS.
> 
> If it all works i don't need to convert anything and i can look at the data
> every minute and it will have the last prices. It's a nice option, now just
> have to get it without errors :-))

Many programmers have tried to overcome these problems, since also many of their
programs, capable of reading MSK files directly, aren't/weren't all that fuzzy in the past,
eg what the MSK or the DL programs are when it comes down to giving proper results,
but now too, these stuborn programmer's programs have also been hit by the Y2K and
the Windows compatability norms and user's correct confusion complaints.