Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Strategies & Market Trends : TC2000 Users Technical Analysis Forum -- Ignore unavailable to you. Want to Upgrade?

To: Iceberg who wrote (2645)	1/8/2000 10:42:00 AM
From: Julius Wong	Read Replies (2) \| Respond to of 3291

OmniTrader still reads data from \TCV3Data and it worked OK. Julius

To: Iceberg who wrote (2645)	1/9/2000 1:00:00 AM
From: Gary Burton	Respond to of 3291

Ice et al--There IS still a problem with using Tc's Export to Text---It still can't be read by most third party programs because the way TC exports it is the reverse of the way many 3rd party pgms read ASCII format files--I found that out the hard way when I used Export to Text and followed all the rules of matching as you descibe in your note in order to properly line up---but i found that it STILL couldn't be read by Advanced GET and Elwave--and when I emailed Elwave and GET's tech support people an example of the ascii file that TC's Export to Text had exported for Alcoa, they both looked at the exact makeup of the exported data fieldand both emailed me back and told me the same thing as to why it still couldn't be read--Elwave then modified their ASCII read at their end a few days ago in order to let their customers have the option of inserting the data the 'other way around' from what is the standard practice, so presumably Elwave can now handle Worden's Export to Text ascii result but GET still can't because they didn't modify at their end to handle the 'mixup' at TC's end when one uses their Export to Text route.----for my part, my Elwave pgm is able to now read TC's non-compliant V3 data (because Elwave designed a recent 'fix' to make non-compliant data to be read in a compliant manner--eg July7,2010 shows up in TC V3 chart for last friday's date but when fed into Elwave it is read as Jan7,2000 by Elwave) and Advanced GET reads TC's V4 directly off the cdrom so i don't bother with V3 for them--so I'm ok for now I guess.