Hi.
i have headcache from importing history data to MC.
i can import data and when iam in offline mode it`s working fine
but when i connect to realtime .
its show all history data till i didnt press CTRL+R .(refresh chart)
then strange behavior it delete my history and only realtime data are showing
why this happend ?
in QuoteManager i can see after import there are data but when i click Ctrl+R anytime in chart
and then go to Quotemanager and check again data (edit data) i see it deleted my old data.
iam importing only EOD data. i guess Minute data works fine after refresh as well.
Import Data Problem Again and Again Again
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 489 times
Re: Import Data Problem Again and Again Again
Dear flimbo,
Please tell us in what symbol do you import the data. What is the data source? Also, please tell us what settings do you have inthe Format Instrument window. Do you use Merge feature? If yes, what do you use for History and Real-Time?
Please tell us in what symbol do you import the data. What is the data source? Also, please tell us what settings do you have inthe Format Instrument window. Do you use Merge feature? If yes, what do you use for History and Real-Time?
Re: Import Data Problem Again and Again Again
I will make video using screencast how i am doing it and where is problem.
will post it soon
will post it soon
Re: Import Data Problem Again and Again Again
I've experienced the same issue. Reload (Ctl + R) erases the entire history for the symbol in the database and attempts to refresh from the real time data source, which naturally does not include the imported ascii file data. What is even more frustrating, "Reload 1 day back" wipes out the history in the database as well.
It would be nice if "reload all" simply refreshed the data range specified for the selected chart, and reload for the smaller timeframes (1 day, 2 day etc) was limited to that smaller data range.
It would be nice if "reload all" simply refreshed the data range specified for the selected chart, and reload for the smaller timeframes (1 day, 2 day etc) was limited to that smaller data range.
Re: Import Data Problem Again and Again Again
thats big issue coz i want have history for about 20pairs.
and import it everytime would make me crazy.
i guess this problem will remain till next version will be released.
and import it everytime would make me crazy.
i guess this problem will remain till next version will be released.
-
- Posts: 117
- Joined: 08 Nov 2005
- Been thanked: 3 times
Re: Import Data Problem Again and Again Again
some time ago happen w me ......try this
import data-
see in QM if new data was got
close MC and QM
restart computer
open MC w chart you want
maybe after this you don´t have more problems
jo
import data-
see in QM if new data was got
close MC and QM
restart computer
open MC w chart you want
maybe after this you don´t have more problems
jo
Re: Import Data Problem Again and Again Again
Thanks i tried it but unfortunatelly same issue ;(some time ago happen w me ......try this
import data-
see in QM if new data was got
close MC and QM
restart computer
open MC w chart you want
maybe after this you don´t have more problems
jo
iam starting think that its really big problem and only fixing it in next version can solve it.
but this soft its not cheap so its same that have this big issue.
Re: Import Data Problem Again and Again Again
Thanks i tried it but unfortunatelly same issue ;(some time ago happen w me ......try this
import data-
see in QM if new data was got
close MC and QM
restart computer
open MC w chart you want
maybe after this you don´t have more problems
jo
iam starting think that its really big problem and only fixing it in next version can solve it.
but this soft its not cheap so its shame that have this big issue.
- Dave Masalov
- Posts: 1712
- Joined: 16 Apr 2010
- Has thanked: 51 times
- Been thanked: 489 times
Re: Import Data Problem Again and Again Again
Dear Sirs,
This is a known issue which is already in our fix list. We understand that this is a serious issue, however it is not critical. The fix will require some profound changes in program architecture, so we do not expect it to be solved soon.
This is a known issue which is already in our fix list. We understand that this is a serious issue, however it is not critical. The fix will require some profound changes in program architecture, so we do not expect it to be solved soon.