delay an excel trigger

Please post any questions regarding the program here.

Moderator: 2020vision

delay an excel trigger

Postby mouse » Sun Feb 02, 2014 11:20 am

gary, captain sensible or anyone

i seem to get more than one bet per race , when below the betfair min stake, even though i have excel counta, countblank checks etc to ensure column T is empty.
so my question--- is there some sort of wait or delay i can incorporate into my spreadsheet so that an excel trigger in q5 is delayed until a response(if any) has been received from betfair, before moving on to the trigger in q6 etc.
I'm really stuck on this, have spent ages searching forums to no avail

thnx
mouse
 
Posts: 28
Joined: Thu Oct 21, 2010 12:51 am

Postby Captain Sensible » Sun Feb 02, 2014 10:22 pm

Without knowing how your current triggers fire it's hard to advise you. For under £2 bets doesn't the bet ref column just say "pending" until the actual bet reference is returned. That alone will stop the trigger for that horse firing and you could always add an OR statement to count "pendings" to restrict betting on other runners.
User avatar
Captain Sensible
 
Posts: 2923
Joined: Sat Nov 19, 2005 2:29 pm

Postby mouse » Mon Feb 03, 2014 3:33 am

Captain Sensible wrote:Without knowing how your current triggers fire it's hard to advise you. For under £2 bets doesn't the bet ref column just say "pending" until the actual bet reference is returned. That alone will stop the trigger for that horse firing and you could always add an OR statement to count "pendings" to restrict betting on other runners.


captain ( or anyone who wants to chip in),

there is no problem with a repeat bet on the same horse, --yes pending does stop the trigger firing again with my countA check.
What i cant understand is why the trigger sometimes fires a bet to another runner in the same market, even though i have countA(t$5:t$40)=0 as part of trigger copied down column q. as you know counta , counts nos as well as text eg "pending", Is it because the trigger say in Q6 can
still fire before cell T5 shows "pending" etc. If so can i easily delay the trigger in Q6 for about a second or two so that T5 has a chance to return pending etc?

thnx
mouse
 
Posts: 28
Joined: Thu Oct 21, 2010 12:51 am

Postby Captain Sensible » Mon Feb 03, 2014 11:36 am

You need to be checking the actual trigger to see why that's firing twice, what checks are in that to stop it firing bets on horses with identical figures or where horses fit your bet criteria.

I think it's more likely two horses are fitting the trigger criteria and being fired at the same time rather than any delay in pending being entered. BA can fire bets on all runners at once if the trigger cell is populated.
User avatar
Captain Sensible
 
Posts: 2923
Joined: Sat Nov 19, 2005 2:29 pm

Postby mouse » Tue Feb 04, 2014 8:50 am

Captain Sensible wrote:You need to be checking the actual trigger to see why that's firing twice, what checks are in that to stop it firing bets on horses with identical figures or where horses fit your bet criteria.

I think it's more likely two horses are fitting the trigger criteria and being fired at the same time rather than any delay in pending being entered. BA can fire bets on all runners at once if the trigger cell is populated.


thnx for your time on this captain

yes sometimes more than one nag meets thequalifying trigger, but i only ever want to make one bet regardless per race. I dont mind which one. Hence my check of counta(t$5:t$40)=0 as part of trigger down colunm q. but as ive said before this count check is not reliable since sometimes two bets per race.
any suggestions to resolve the problem

thanx
mouse
 
Posts: 28
Joined: Thu Oct 21, 2010 12:51 am

Postby Captain Sensible » Tue Feb 04, 2014 11:28 am

BA can place more than one bet at a time and because your counta routine is only checking that no bets have been placed, it won't stop more than one trigger firing if the bet criteria is met for more than one horse. You need to only be populating the trigger cell Q when the criteria is only met for one horse or if you want only one bet to only one in a series of qualifiers it may be worth using VBA as you'll have better options to drill down the one you actually want to bet on.

Without knowing how your trigger populates it's hard to say what's the best route for you to achieve this.

Lets assume with the odds continually changing there may be an occasion when only one horse fits at that time. We could add an extra criteria to the trigger to only fire when one horse fits, easiest way is probably just having the stake (or odds) column only populated when the criteria is met else it's blank, easily done using an IF. Then within the trigger cell you just add another criteria countA(S$5:S$40)=1 so we only fire when one horse meets the criteria , if your trigger is basing things on something static like the SP we could always have the saddlecloth number used so the lowest or highest gets bet
User avatar
Captain Sensible
 
Posts: 2923
Joined: Sat Nov 19, 2005 2:29 pm

Postby mouse » Wed Feb 05, 2014 8:23 am

Captain Sensible wrote:BA can place more than one bet at a time and because your counta routine is only checking that no bets have been placed, it won't stop more than one trigger firing if the bet criteria is met for more than one horse. You need to only be populating the trigger cell Q when the criteria is only met for one horse or if you want only one bet to only one in a series of qualifiers it may be worth using VBA as you'll have better options to drill down the one you actually want to bet on.

Without knowing how your trigger populates it's hard to say what's the best route for you to achieve this.

Lets assume with the odds continually changing there may be an occasion when only one horse fits at that time. We could add an extra criteria to the trigger to only fire when one horse fits, easiest way is probably just having the stake (or odds) column only populated when the criteria is met else it's blank, easily done using an IF. Then within the trigger cell you just add another criteria countA(S$5:S$40)=1 so we only fire when one horse meets the criteria , if your trigger is basing things on something static like the SP we could always have the saddlecloth number used so the lowest or highest gets bet



Ok , i can see where i've been going wrong.
will try out some ideas in the last paragraph. spot on with the right advice again captain.

many thnx, over and out
mouse
 
Posts: 28
Joined: Thu Oct 21, 2010 12:51 am


Return to Help

Who is online

Users browsing this forum: No registered users and 65 guests

Sports betting software from Gruss Software


The strength of Gruss Software is that it’s been designed by one of you, a frustrated sports punter, and then developed by listening to dozens of like-minded enthusiasts.

Gruss is owned and run by brothers Gary and Mark Russell. Gary discovered Betfair in 2004 and soon realised that using bespoke software to place bets was much more efficient than merely placing them through the website.

Gary built his own software and then enhanced its features after trialling it through other Betfair users and reacting to their improvement ideas, something that still happens today.

He started making a small monthly charge so he could work on it full-time and then recruited Mark to help develop the products and Gruss Software was born.

We think it’s the best of its kind and so do a lot of our customers. But you can never stand still in this game and we’ll continue to improve the software if any more great ideas emerge.