Rank: Advanced Member
Groups: Registered, Registered Users, Subscribers, Unverified Users
Joined: 10/28/2004(UTC)
Posts: 3,111
Location: Perth, Western Australia
Was thanked: 16 time(s) in 16 post(s)
|
Asish,
I moved this post from its original location to start a new thread becuase it raises some interesting issues that should be discussed, not under the umbrella of the RMO trading system.
--
I am not too sure whether MS10 and any previous versions will 'play happily' on the same computer, but I do know that having multiple versions of MS can lead to issues with maintaining data and your personalised indicators, explorations etc.
It is definately possible to have multiple versions of MS on the same machine but there are some dangers, difficulties, hassles, traps etc
Data
When you open a 'data file' in MS a smart chart is created in a sub-folder of the folder containing the original data. This smart chart has embedded in it the details of which version MS created the smart chart. If you try to open a stock for which a smart already exisits, and the version of MS used to subesquently open the chart is older than the version that created the chart in the first place, an error is generated. If you use a newer version of MS to open a smart chart created by an older version, the older version is replaced the newer version.
This means that you have to clean out the newer-version smart charts each time you want to use an older version of MS. This can cause all sorts of troubles for people who may not have a good grasp on exactly what they are doing as they often end up deleting data instead of the smart charts.
One way to avoid this is to have multiple copies of your data; one for each version of MS you have. It goes without saying that some people have limited hard drive space and can ill-afford to have two copies of exactly the same information. There is also the issue of keeping every version of the data up-to-date when you do your data dwonloads; imagine the complexities of multiple versions of intraday data.
In short, its probably better to choose the version of MS that you are most comfortable using or that version which has all the tools you need to trade. This alleviates the need to have multiple copies of the data, or 'playing' inside your data directories.
(Of course, there are other methods to opening charts and data management but in the end, having multiple versions of MS on the same machine adds an unnecessary level of complexity and management - - another place where something else can wrong!)
Code
Unfortunately, codes are not shared between different versions of MS. You cannot write a function and store it in some sort of central code repository and have this function accessible by all versons of MS on your machine. (Equis: this functionality would be REALLY USEFUL to have any future versions or upgrades!)
This means that whenever you write a MS9 function, you will have to do some sort of management to have that function available in MS10 or any other function.
When you small numbers of functions in addition to those built-in functions of MS, then this is not too much of an issue, but when you have vast numbers of functions, explorations, system tests etc thia management can be quite difficult, if not down-right dangerous.
Again, if you don't need to make life difficult for yourself, don't. Keep the better version of MS and archive the other one. Trying to synchronise codes across multiple versions of MS on the same
machine adds an unnecessary level of complexity and management - -
another place where something else can wrong (deja vu!)
If you absolutely insist on having multiple versions running on the same machine, let us know and we can continue the discussion on data and code synchronisation. Maybe some others can join in with their experiences - - I hate doing all the talking!
Hope this helps.
wabbit [:D]
|
