|
PureBytes Links
Trading Reference Links
|
I use Ascii data with TS very frequently and have run into the
described problem many times. It can be EXTREMELY frustrating!!! It
can even happen when creating new charts from ASCII data files that I
have already successfully set up a chart for.
I have found the cleanest fix to be the following.
1. Using server data, set up a chart using the same time frame as the
desired ASCII data.
2. Go to View/Data Window and do a "Send to File" command", naming it
the same name that you want to use for the ASCII data.
3. Open that file up in a word processor or spreadsheet and delete the
first line (the one with the labels). Then save that file using the
same name and close it.
4. Open a chart up and import that ASCII file as
"Date/Time/O/H/L/C/V/OI"
5. Save and close the workspace.
6. Replace the data in that ASCII file with the data that you really
want to use (your original ASCII data). Make sure to close the file
after doing so.
7. Open the workspace that you originally saved the imported chart in.
Wah-La! You should have a chart with the data that you originally
wanted.
Don't ask me why it works. IT JUST DOES! My best guess would be that
there is some sort of formatting that needs to be read on the FIRST
opening of the ASCII file. If it isn't there, TS screws up the reading
of the data. But then, that's just a guess.
Hope this helps.
Bob Hunt
----------------------------
DStan34930@xxxxxxx wrote:
>
> I use this asci data all the time. In fact, I currently have charts set up
> in another workspace that uses it just fine.
> However, when I attempted to produce duplicate chart windows in
> another workspace today.......
>
> I used the following data(the following are portions for example).....
>
> 10/13/98,1615,1003.00,1004.00,1002.50,1002.50,19,23
> 10/13/98,1620,1002.70,1003.00,1002.70,1003.00,2,0
> 10/13/98,1625,1003.50,1003.50,1002.50,1002.50,1,2
> 10/14/98,0935,995.50,997.00,994.50,996.50,22,19
> 10/14/98,0940,996.00,1000.00,995.50,998.50,22,16
> 10/14/98,0945,999.00,999.50,995.50,997.00,18,20
>
> and it always comes out like this.....
>
> 10/13/98,1605,1003.00,1003.00,1003.00,1003.00,1,0
> 10/13/98,1610,1004.00,1004.00,1004.00,1004.00,1,0
> 10/13/98,1615,1003.50,1003.50,1003.50,1003.50,0,1
> 10/13/98,1620,1002.50,1002.50,1002.50,1002.50,0,1
> 10/13/98,1625,1003.00,1003.00,1002.50,1002.50,1,1
> 10/14/98,0940,996.50,996.50,996.50,996.50,0,1
> 10/14/98,0945,998.50,998.50,998.50,998.50,1,0
> 10/14/98,0950,997.00,997.00,997.00,997.00,0,1
>
> 1) the problem only occurs when attempting to create new charts
> using the most recent 2 contracts only.
> 2) the same problem occurs whether applying a template or not.
> 3) the problem occurs no matter which workspace I attempt to create charts.
> 4) the field chosen when inserting data is correct.
> "DATE","TIME","O","H","L","C","V","OI"
> 5) the data works in existing charts.
> 6) scandisk finds no errors.
> 7) altering the amount of data to chart has no effect.
>
> Any ideas?
>
> dbs
|