Calling GeorgeUk

[GeorgeUK]

Castillo, you may be better off starting a new thread so your specific queries can get answered as it develops.

That said, have a look at this thread
http://www.gruss-software.co.uk/forum/v ... =5715#5715

The last piece of code i did was to copy the data every time there was an update. If BA updates every second, this would only record about 4 min worth of data as there are only 255 columns to use, but if we were to put it in the rows, there are 65536 so that's just over 18 hours.

Tell us what you need and we'll try to get you sorted.

Note to Horseman - If you're reading this, i swear i am still looking at the autobet workbook. Fixing one part and then finding another part that may not work depending on user specifications. It's turning into a monster.

[Castillo]

Castillo, you may be better off starting a new thread so your specific queries can get answered as it develops.
Tell us what you need and we'll try to get you sorted.

George

Thanks for the reply. Basically what I had in mind is the following, whether it can be done maybe another matter
The current odds available are displayed in the range F5:F35, would it be possible to record the history of odds as they change in the range
F5:F35 to ranges Y5:Y35,Z5:Z35 & AA5:AA35 (the next 3 columns after the Profit/Loss column). So you will end up with 4 sets of odds per selection with F5 being the current odds Y5 being the next change, Z5 being the next change after Y5 & AA5 being the oldest change after Z5. So it could well look like the following

F5 4.1
Y5 4.2
Z5 4.4
AA5 4.5

I sometimes use WOM (Weight Of Money) to indicate whether a selection is a drifter or a steamer, but if the above was possible it would certainly be another alternative. I apoligise for asking on this Topic, if you feel it requires a new thread I will start one off.

Cheers
Castillo

[GeorgeUK]

Hi Castillo - didn't quite get what you were driving at earlier, but it's definately relevent to what we've already done in this thread. Unfortunately it's going to get alot more complicated.

At a glance - i think we'll need a macro similar to the one already made, but for each row. The problem will be that all the cells will change on each refresh, but the values in the cells may not change, so the memory will need to store what each cell had as a value before the change - to check whether that cell has a different value, then update the columns at the end of the sheet.

Can't think of an easy way to do this, but will look into it more.

Might end up copying the data to sheet2 column B and on each refresh, the previous refresh data would be in column A. If there are any changes, make the ammendments in the appropriate row in your end columns and delete column A on sheet2 - ready for the next refresh to be put into column B.

Not the same as we had before, but may be easier than trying to save all that data into memory - just put it onto another sheet to compare. The end columns we can probably have a worksheet_change event monitoring them and then carry the data to the other cells.

Never looked at WOM before. Would the most recent values be in column Y or AA? because the newly refreshed data from sheet 2 may need to be copied to AB.

Alot to look at and think about - but probably doable. (Please note the "probably" )

[Castillo]

Would the most recent values be in column Y or AA? because the newly refreshed data from sheet 2 may need to be copied to AB.

Hi George

Thanks for the reply. The most recent values could be in column Y or AA. I was looking to change data only when the odds change and not by each second refresh. I have looked at your previous code which updated F12 from F5 and this is exactly what I would be looking at, it works extremely well. From my earlier post if this was true F5 4.1, Y5 4.2, Z5 4.4, AA5 4.5 (Y5 being the most recent change) this selection would be a definite steamer and a back bet followed by a 1 tick lay bet may well be worth it. Gary has suggested the tick offset feature will soon be available to trigger from excel and this is what I'm trying to prepare for. Many thanks for your offer of help.

Cheers
Castillo

[GeorgeUK]

The only problem i can see is that i was holding the value of F5 in memory until it changed to a different value. The code was running on each refresh so it had to hold a value for more than one refersh. I can't see a way of holding F5:F35 in the memory - so i think transferring data to sheet2 is the only way without alot of code being used.

Can't look at it this weekend as i'm going out. Will come back to it though.

[Castillo]

Can't look at it this weekend as i'm going out. Will come back to it though.

Many thanks George.

Cheers
Castillo