|
PureBytes Links
Trading Reference Links
|
<x-html><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type>
<META content="MSHTML 5.00.2314.1000" name=GENERATOR></HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>Here's a Y2K problem for the history books, and none of the
price history was carried into the new symbols because this problem is
unexpected.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2>Joe</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><B>-----Original Message-----</B><BR><B>From:
</B>Qcharts <<A
href="mailto:qcharts@xxxxxxxxx";>qcharts@xxxxxxxxx</A>><BR><B>To: </B><A
href="mailto:jehardt@xxxxxxxxxxxxxx";>jehardt@xxxxxxxxxxxxxx</A> <<A
href="mailto:jehardt@xxxxxxxxxxxxxx";>jehardt@xxxxxxxxxxxxxx</A>><BR><B>Date:
</B>Monday, January 03, 2000 07:22 AM<BR><B>Subject: </B>Future Symbol Lookup
Problem<BR><BR></DIV></FONT>An unforseen issue related to the decade rollover
has caused a futures symbol <BR>translation problem in the servers providing
service to QCharts, LiveCharts, <BR>third-party QFeed applications, and the
Quote.com/Lycos web site.<BR><BR>Any futures contract with a delivery month in
the year 2000 will be<BR>updating under a new symbol indicating an expiration in
the year 2010. For<BR>example: SP00H is now updating under the symbol
SP10H.<BR><BR>Here is the exact syntax:<BR><BR><root
symbol><00><month code><BR><BR>will be available through symbols
formatted:<BR><BR><root symbol><10><month
code>.<BR><BR>Example (This weeks data for):<BR>"SP00H" will be available via
symbol "SP10H"<BR><BR><BR>We apologize in advance for any inconvenience this
temporary situation<BR>may cause you. We will correct the problem as soon as we
possibly can.<BR><BR><BR>We appreciate your business and thank you for
your<BR>patience and understanding regarding this matter.<BR><BR>Richard
Mocek<BR>Development Manager, Continuum
Technologies<BR>Quote.com/Lycos<BR><BR><BR></BODY></HTML>
</x-html>From ???@??? Mon Jan 03 13:44:41 2000
Return-Path: <majordom@xxxxxxxxxxxxxxxxxx>
Received: from listserv.equis.com (listserv.equis.com [204.246.137.2])
by purebytes.com (8.8.7/8.8.7) with ESMTP id LAA20914
for <neal@xxxxxxxxxxxxx>; Mon, 3 Jan 2000 11:14:17 -0800
Received: (from majordom@xxxxxxxxx)
by listserv.equis.com (8.8.7/8.8.7) id KAA14044
for metastock-outgoing; Mon, 3 Jan 2000 10:05:09 -0700
X-Authentication-Warning: listserv.equis.com: majordom set sender to owner-metastock@xxxxxxxxxxxxx using -f
Received: from freeze.metastock.com (freeze.metastock.com [204.246.137.5])
by listserv.equis.com (8.8.7/8.8.7) with ESMTP id KAA14041
for <metastock@xxxxxxxxxxxxxxxxxx>; Mon, 3 Jan 2000 10:05:06 -0700
Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62])
by freeze.metastock.com (8.8.5/8.8.5) with ESMTP id KAA22504
for <metastock@xxxxxxxxxxxxx>; Mon, 3 Jan 2000 10:14:50 -0700 (MST)
Received: from 216-164-139-178.s432.tnt5.lnhva.md.dialup.rcn.com ([216.164.139.178] helo=erols.com)
by smtp03.mrf.mail.rcn.net with esmtp (Exim 2.12 #3)
id 125ApD-0005F8-00
for metastock@xxxxxxxxxxxxx; Mon, 3 Jan 2000 11:59:20 -0500
Message-ID: <3870D598.BC0AB4F8@xxxxxxxxx>
Date: Mon, 03 Jan 2000 12:00:09 -0500
From: scheier <scheier@xxxxxxxxx>
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: metastock@xxxxxxxxxxxxx
Subject: Re: file size limits in tc2000 or MS
References: <0.675fdf86.25a21b37@xxxxxxx>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-metastock@xxxxxxxxxxxxx
Precedence: bulk
Reply-To: metastock@xxxxxxxxxxxxx
Status:
Interestingly, the limit was originally imposed by Metastock, so TC2000 would
simply have been complying. Each directory of Metastock files has its own
directory index, called master or emaster. I understand that the new
versions of metastock no longer impose this limit, but other software using
metafile as a format option are probably still using this older convention.
It would now be TC2000's turn to catch up, I think.
TONE9739@xxxxxxx wrote:
> can anyone explain why tc2000 limits file size of 255 symbols when
> transporting to metastock files
> i would prefer to use tc2000 scans to filter stocks but do not want a limit
> on file size to MS - i want to do the TA work done in MS
> who is setting the 255 symbol limit - tc2000 or MS and can anything be done
> about it?
|