Quote:
Is it possible to have the same jforex live account run on different computers simultaneously?
Yes, no problem.
Quote:
Then also have different or same strategy run on each computer for the same account?
Yes, no problem. There is no limitation, but you have to know what the strategies doing (see below). The errors you have mentioning are probably coming from the way your strategy working, and not from the fact that the same strategy running on multiple computers.
Quote:
If yes, does this only work in live or also in demo account?
There is for sure no difference how Demo and Live working/acting on this manner.
Things to keep in mind:
If you strategies operating on orders in general (orders that are bind to the account), you can face some problems. As one strategy instance doesn't know which orders was created by itself. To solve this, you have some options:
- Let you strategy handle its own orders within a Set. Whenever the strategy submits and order, it places it in the Set, and from that moment you can operate on orders within the Set only. Each strategy will have its own Set. One problem with this if the strategy stops. Then you loose your Set, so after a restart you won't know which existing order was created by which strategy instance.
- Introduce a unique strategy identifier, which is used in the order (for example, in the comment part). Same goal is reached: a strategy can see from an order if it was created by itself. This is even better, as if the strategy stops for whatever reason, after a restart you can immediately see from an order, which strategy created it.
As you have mentioned different time parameters, you can also try to make different strategies for different time periods. So you will handle 1M orders with one strategy (maybe 2 or more on more computers), and another period type with a different strategy. You have to use the above mentioned tips to identify an order's parent (creator) strategy, but you will have a cleaner picture of what strategy doing what.
You have mentioned some istrategy erros. More useful information could be provided if you be more specific on this: What happened, what is the exact error, where do you see this, how is it possible to replicate the issue, maybe a sample strategy that doing the same (generating the error), etc, etc.
