|
PureBytes Links
Trading Reference Links
|
Allan,
It is also kinda neat the way they put a fix for a bug
into the next version and then charge to upgrade. A first, as far as I
know, for the software industry. As for AmiBroker, the enhancement
of their AFL language by including script, as well as multiple stock
backtesting is a huge jump forward. If they get their act together with
respect to charting tools, which I think is their weakest point but is promised
in the next major upgrade, they will be very hard to stop, even if one does not
look at price.
Bill
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
----- Original Message -----
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black">From:
Allan Wade
To: <A title=metastock@xxxxxxxxxxxxx
href="mailto:metastock@xxxxxxxxxxxxx";>metastock@xxxxxxxxxxxxx
Sent: Friday, August 10, 2001 4:15
PM
Subject: RE: Equis have updated their
Symbol database at last ***CAUTION***
I wish those goof off's ay Equis would get their act
straightened out. Thismeans that I went through a reinstall (and
indicator/system testerconversion) for nothing. They could have just
emailed me some/any correctversion of the file. I guess I just fell for
the 2 oldest tricks in the techsupport book....."Reinstall it"...and "it
will be fixed in the nextrelease".Amibroker is looking better and
better.Allan WadePhoenix, AZemail: <A
href="mailto:allanwade@xxxxxxxx";>allanwade@xxxxxxxx -----Original
Message-----From: <A
href="mailto:owner-metastock@xxxxxxxxxxxxx";>owner-metastock@xxxxxxxxxxxxx
[mailto:owner-metastock@xxxxxxxxxxxxx]On Behalf Of neoSent: Friday,
August 10, 2001 4:46 AMTo: <A
href="mailto:metastock@xxxxxxxxxxxxx";>metastock@xxxxxxxxxxxxxSubject:
RE: Equis have updated their Symbol database at last ***CAUTION***This
is an email from MS support:The problem was with the symbol database
files on the server. During themigration from one server to another, these
files were damaged. Thisproblem was not specific to any one version. The
problem has beenresolved. You should be able to update the symbol database
from anyversion,
again.Thanks,Lynn
|