version 66x18

[mak]

Gary hi
i know that you are busy these days but please have a look at the following when you find some time.

I just installed 66x18 version, & tried to log my bots from multiple quick link
2 for the time being are working fine.
The 3rd when it tries to move to next market is just freezing with the screen showing "Market Loading" and stays there.The worst is that even when i don't see any market at grid interface if i click the mouse where the back side is for example it is working & it tries to place a bet!! or sometime it opens the chart window -depending on where i tick the mouse in the blank page...Hope that make sense

Probably some more members will have the same problem i believe, but i am also curious why the other 2 bots are working?

Thanks

[mak]

Just to add that even when i try to un-log the sheet from BA nothing changes
It still shows market loading...and the green indication that a sheet is attached to tab is still there.

[mak]

Just realize that it has to do with multiple sheets quick link
I manually log the sheet to BA & it is working...

[GaryRussell]

When you get chance can you try the quick link option again and do the following when it stops working.

Can you send the log file name BA_Diagnostic.txt in "c:\temp\Betting Assistant Logs" folder to admin@gruss-software.co.uk

On the problem tabs select "Display Excel Link Activity" from the Excel menu, copy the log and send to the above address.

[Spike]

Hi Gary, I'm sorry to bother you right now but unfortunately I also have a problem with the latest Beta which I've had to switch to because of the date thing;

The "wait for result" parameter isn't working on ba.placebet (com). If it's an easy fix I would really appreciate it as I've become fairly dependent on it.

[GaryRussell]

Hi Gary, I'm sorry to bother you right now but unfortunately I also have a problem with the latest Beta which I've had to switch to because of the date thing;

The "wait for result" parameter isn't working on ba.placebet (com). If it's an easy fix I would really appreciate it as I've become fairly dependent on it.

Is there an error message or does it still wait for the result even if you setWaitForResult to false? I've just tested it again and it appears to be working.

[GaryRussell]

Also you might be interested to know that this version also has a new event: betPlaced(ref:String,selecId:Integer,AvgPriceMatched:Double,sizeMatched:Double,resultCode:String,token:String)

You can pass a string value to placeBet which is passed to the betPlaced event so that you can match them together.

eg. ba.placeBet 0, "L", odds, 2, False, "bet1" where "bet1" is the token passed to the betPlaced event.

[Spike]

It said something like "too many parameters"

I'll have a look again at lunch time- maybe I made a mistake when I was testing it. Unfortunately I'm not by my computer untill then.

[mak]

just sent you email

[GaryRussell]

It said something like "too many parameters"

I'll have a look again at lunch time- maybe I made a mistake when I was testing it. Unfortunately I'm not by my computer untill then.

That could be the COM server needs re-registering because of the changes I made to add the betPlaced event. Uninstall and re-install, it should fix it.

[Spike]

Ok, I'm getting "wrong number of arguments or invalid property assignment" coming up in excel- and the debugger is going straight to the placebets line.

I'm testing it by using the testbacom example sheet, simply adding "False" to the "test back" code.

[Spike]

Forgot to say- I reinstalled BA and tried removing and the replacing the reference to bettingasistantcom (restarting excel inbetween). Is this what you meant?

[Spike]

I also tried disabling and re-enabling the com from within BA- no joy.

[Spike]

Actually I've got version 66W3- (the new beta) could that be the problem?

[mak]

are you talking to you?