SI
SI
discoversearch

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

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Iceberg who wrote (2642)1/8/2000 12:45:00 AM
From: Gary Burton  Read Replies (1) of 3291
 
Ice--I think the problem is that the V3 data for Jan is "out of date sync"--In V3, jan3 now shows up as Mar3,2010 , jan 4 is recorded as Mar4,2010 etc etc---many 3rd party pgms can't handle an out of sync date sequence---I use Elwave (an elliott wave pgm out of the Netherlands) and they just came out with an upgrade that in effect made noncompliant data compliant again when read by Elwave---TC2000 V3 reads Jan 7 as Mar7,2010 but when this is fed into Elwave, the Elwave charts shows it as Jan7,2000.---Many other 3rd party pgms haven't devised their own fix for reading out of order dates yet. Elwave just did so this week. Advanced GET (a competitor to Elwave)can't read the noncompliantV3 yet either. I gather they said the hell with it ,let's just now read V4 directly
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext