PureBytes Links
Trading Reference Links
|
Telescan blames Equis and Equis blames Telescan for the problems with
downloading from Telescan. This has been ongoing for several years and no
one is working on a solution.
Telescan did tell me that the Equis Downloader was one of 2 downloaders
that give them problems. I have solved the problem by dropping Telescan
and bypassing the Equis Downloader for downloads.
I would probably agree with Forman that Telescan are indifferent. On the
other hand Equis has its own share of errors and omissions. Neither is
without fault.
One of the major problems is that Equis doesnt appear to want to do a major
overhaul. Metastock needs to be completely rewritten using state of the
art methodologies.
At this point I'll get off my soapbox.
Lionel
-----Original Message-----
From: Equis Support <support@xxxxxxxxx>
To: 'beck@xxxxxxxxxxxxxx' <beck@xxxxxxxxxxxxxx>
Cc: 'metastock@xxxxxxxxxxxxx' <metastock@xxxxxxxxxxxxx>
Date: Wednesday, January 27, 1999 12:49 PM
Subject: RE: I'm outraged
>Joel,
>
>The representatives thought yesterday when you were sent the email was
>to have you on the newest possible playing field. It wasn't sent to
>solve the Telescan collection problem, but because we would rather not
>try and solve a problem in an earlier version than necessary. It will
>not solve the Telescan collection problem because the problem is not
>solvable by Equis. However, since yesterday's email does not pertain
>to MetaStock Professional, the human error of thinking you were using
>MetaStock for Windows 95 & NT was made by the answering representative,
>which by the way may have been totally different than the representative
>you corresponded with two weeks earlier. I apologize for the fact this
>representative made an assumption. You are correct regarding the
>MetaStock Professional patch not having changed. This miscommunication
>over versions can be alleviated if the program name and version is
>included in all support request emails.
>
>The Telescan problem is continuing. I call you attention to the
>following from our 1/13/99 email to you:
\\snip
|