Moderator: 2020vision
by mouse » Sun Feb 02, 2014 11:20 am
by Captain Sensible » Sun Feb 02, 2014 10:22 pm
by 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.
by Captain Sensible » Mon Feb 03, 2014 11:36 am
by 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.
by Captain Sensible » Tue Feb 04, 2014 11:28 am
by 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
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.