+1 888 340 6572
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Closed Feature request MC-2279

allow multiple data sources for metastock data.

action_vote_minus_faded.png
2
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
icon_info.png This issue has been closed with status "Declined" and resolution "Not determined".
Description
Please see original email below

Summary of problem:
MC only allows one Metastock data source . If a user has MS data for multiple exchanges or markets, these will be separate dirs because of symbol naming overlap
I would like MC to allow multiple data sources ( ie dirs) for the MS data source



+++++++++++++++++++++

I'm using MC v10.0

I have MS data for 2 different markets ( USA and ASX) , there are some symbols which are the same ie symbol names are not unique and overlap between the 2 markets

I currently have the dirs for the USA market specified in the data source settings and everything works ok

Now I want to add another data source for the ASX but MC doesnt seem to allow that ( I'm sure a version from many years ago used to allow you to setup multiple data sources for MS data.)

I cant just add the ASX dirs to the existing data source because of the symbol overlap

Is there any way to add another MS data source ?

thanks
Ivan
Comments (2)
#1
user-offline.png  Kaos (kaos101)
Jul 22, 2017 - 02:17

For the area Quote Manage > Tools > Data Sources > Metastock > Settings

Two features that might need to be discussed:

1) When add a metastock directory -> add in an Exchange Identifier so all symbols in that directory get added to that exchange

2) Import / Export buttons for a csv file of metastock directories + exchange identifiers

#2
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Aug 01, 2017 - 05:06
It is not planned for future, as requires multiple changes in the data feed structure and significant amount of work should be done. This does not fit into our current roadmap.
History
Issue basics
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates