Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Mon, 06 May 2024 00:31:50 +0000
Post From: [User Discussion] - Message to all OEC users
| [2014-03-12 23:17:54] |
| |
|
We do have a communication channel to OEC developers. At this point, based on the communication we had with them today, they do recognize the problem and we know they are competent to understand it and resolve it. It is our belief that it should be taken care of in the next few days. The normal OEC customer support is not going to be effective with this particular issue. We will persist with OEC developers on it until it is resolved. In the past we requested that users contact OEC support about this, but it does not seem as though that is helping because they really do not believe there is a problem or do not know what to do about it or do not understand it (or a combination of these). Additional Message Logs may be helpful. We will forward the relevant content in those to OEC. Although probably we only need one or two logs. This really only highlights the difference between a business like OEC and Sierra Chart . Obviously we are different businesses but there are important key differences we would like to point out. Support for Sierra Chart is handled by the people who develop Sierra Chart. It is not handled by customer support because they are not going to be qualified to provide support for advanced software like Sierra Chart that works across a wide range of data and trading services. Unfortunately this is what makes our work very difficult because we have to allocate time to development and also to support. The majority of the code within Sierra Chart we 100% control which is the reason why we do not use API components. This is also reason why we are developing our own spreadsheets to replace an external spreadsheet components that we did not develop. The reason this is so important that we 100% control the code and the code is low-level code that works directly on top of the operating system is that when there is a problem, we can track it down reliably and resolve it. There is no guess work and we are completely in control. In the case of OEC, they are using .NET and may be using some kind of FIX engine that they did not develop. This makes troubleshooting more difficult on their side. They might disagree and they will know best. But still having 100% control of code makes problem-solving easier. As long as qualified developers have developed it and are working on it. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-03-13 01:12:43
|