Questions about COM VB program

[ians1711]

Finally got a COM program working. Have a few questions about what I am seeing:

First - the VB code goes to sleep between 10pm and 11am. At 11am it finds the "Horse Racing - Todays Card" sport and then scans the list of events looking for the first race of interest. When found, I call openmarket. But nothing happens. All subsequent calls work OK. Got a chance to check the status of BA today at 11am. If I look at the markets list, the race I tried to open is highlighted, but the race itself hasn't been loaded into the tab. Anyone else seeing this or can explain?

Second, sometimes when I find a race I haven't seen before, it is already in a CLOSED state, so I ignore it and move on to the next race. However my code is also ignoring the next race which isn't CLOSED. How long should I be waiting after calling openmarket before I can safely assume that the fields in the main body of the worksheet that are populated by BA refer to the next market - I am assuming that I am checking too quickly and still seeing the CLOSED state from the repvious market?

Third - I had to shut down BA and EXCEL, and when I restarted I opened two tabs in BA and connected the second tab to the worksheet with the VB COM code. When this started running the openmarket call was loading the next market into the first tab - does the com interface only work on the first tab?

Thanks
Ian S

[GaryRussell]

First - the VB code goes to sleep between 10pm and 11am. At 11am it finds the "Horse Racing - Todays Card" sport and then scans the list of events looking for the first race of interest. When found, I call openmarket. But nothing happens. All subsequent calls work OK. Got a chance to check the status of BA today at 11am. If I look at the markets list, the race I tried to open is highlighted, but the race itself hasn't been loaded into the tab. Anyone else seeing this or can explain?

I will look into this.

Second, sometimes when I find a race I haven't seen before, it is already in a CLOSED state, so I ignore it and move on to the next race. However my code is also ignoring the next race which isn't CLOSED. How long should I be waiting after calling openmarket before I can safely assume that the fields in the main body of the worksheet that are populated by BA refer to the next market - I am assuming that I am checking too quickly and still seeing the CLOSED state from the repvious market?

It's due to the multi threaded nature of the program. There is a small delay before the prices are loaded after the market is loaded. Once cell N3 contains the market id you just opened you can rely on the status.

Third - I had to shut down BA and EXCEL, and when I restarted I opened two tabs in BA and connected the second tab to the worksheet with the VB COM code. When this started running the openmarket call was loading the next market into the first tab - does the com interface only work on the first tab?

It only works with the first tab at present. Proper multi tab page support will be added in the future, but in the meantime there is an undocumented property: tabIndex. Set it to 0 to for the first tab, 1 for the second etc. That is the only way you can currently access more than one tab, you can't open or close tabs, etc.

[ians1711]

Gary
Thanks for the quick response
Ian S

[ians1711]

Gary
By the way - I'm running version 66w
Ian S

[ians1711]

Gary
Found the following in the BA_Diagnostic.txt file. Since the messages are also output at other times when the market switch has worked successfully I am not sure whether they are relevant:

11:01:01:838: Attempted market change, but requests are pending.
11:01:02:229: retried market.

Ian S

[GaryRussell]

They are not relevant. Can you confirm you have this problem every time the VBA code has been idle for an hour?

[ians1711]

Gary
I guess so. Happens every morning - not sure what you mean by idle. The Excel VB code is executing every refresh waiting for the time to reach 11am

Ian S

[GaryRussell]

Gary
I guess so. Happens every morning - not sure what you mean by idle. The Excel VB code is executing every refresh waiting for the time to reach 11am

Ian S

I was referring to what you said

the VB code goes to sleep between 10pm and 11am.

although I suppose "idle" isn't the correct word.

I am still looking into it.