Bloubul,
I explained to you via email after your enquiry last year that I dont yet have access to the original spreadsheet that generated the temperature zone graphic displayed on my website, due to hard drive failure on that PC and the backup being corrupted. Even if I had I can tell you that it required knowlege of lookup tables and Macro programming in order to extract and translate a temperature score to that graphic layout. Thats a fair amount of work if you dont have those particular skills, and I wonder if it is worth it. I do not intend to reproduce that graphic now that my website is abandoned ( and looking worse for wear).
http://www.lotterygen.co.uk/temperature_page.html
I would suggest that if you are not running a website you do not need to produce a layout in that format anyway, all you need is a table of heat scores and a way of grouping your numbers within the defined limits of temperature zones you have defined. That is if its for your own personal use.
The easiest way is as Icewynd suggests, to use conditional formatting, except that if you have ten temperature zones like I did, you need ten conditional formatting rules applied to each ball in order to highlight each ball according to your temperature limits. That can be tedious if you are not used to conditional formatting.
However, once conditionally formatted you can copy and paste the table and sort by 'temperature score' - this will produce colour 'bands' where the balls have been grouped adjacent to each other according to score and hence colour.
Apart fom that you need a system which allows you to create a temperature score in the first place, there are loads of ways of doing this, limited only by your imagination. Usually it will be based on skips or frequency or a combination of both. For my website I used a weighting system that took into account not just the fact that a ball had been recently drawn, but how recently, and a figure was calculated accordingly. Have you done this ?
I'll be posting a demo spreadsheet shortly with a just one way of doing it. It incorporates some of the ideas I had 23 years ago when I first did this, but not exactly the same, and I wont be writing any macros.
Frank