|
|
Home
Search
Register
Login
Recent Posts
»Forums Index
»Archive (2017 and earlier)
»IQFeed Developer Support
» Protocol 5.1 - Invalid Symbol
|
|
| Author | Topic: Protocol 5.1 - Invalid Symbol (3 messages, Page 1 of 1) |
 dplneural -Interested User- Posts: 11 Joined: Sep 11, 2009 |
Posted: Apr 2, 2014 10:19 PM
Msg. 1 of 3
I compiled the sample LevelOne app using MSVC 2008 on both Windows 7 and Windows 8 OS and if I don't use Protocol 5.0 or 5.1 and request GBPUSD.FXCM as a watch I get the correct data and fields as requested. If I use Protocol 5.0 or 5.1 I get an invalid symbol message. Is there something I am missing here...see attached image...thanks in advance
File Attached: Symbol_Not_Found_Windows_8.png (downloaded 1343 times) |
|
dplneural -Interested User- Posts: 11 Joined: Sep 11, 2009 |
Posted: Apr 3, 2014 08:18 PM
Msg. 2 of 3
the simple solution to this problem was to add a TrimRight() to the symbol string before formatting the command...eg:
CString csCommand(m_csUserData); csCommand.MakeUpper(); if (m_csUserData == csCommand) { // add this line // m_csUserData.TrimRight(); csCommand.Format("w%s\r\n", m_csUserData); m_IQConnectSocket.Send(csCommand, csCommand.GetLength()); } |
|
DTN_Tim Walter -DTN Guru- Posts: 1238 Joined: Apr 25, 2006 
|
Posted: Apr 7, 2014 08:58 AM
Msg. 3 of 3
Hello,
Thanks for the update. Glad to hear you were able to figure it out. Tim |
|
|