BerkshireBlue
Well-Known Member
- Joined
- 19 Jan 2015
- Messages
- 4,040
No need to worry mate, this is used for genuine Excel work, which databases would not be suitable for. A real life example where this could be used, and which I have created, is preparing a sports league table. In its simplest form, all the teams would be listed in alphabetical order, and their results entered in a separate area on the spreadsheet. Points attained are calculated, and entered alongside each team. These points totals are then ranked using Excel's RANK function. A separate table is then used to show the league table, with real time updates every time a new result is entered. The league table has the positions listed from 1 to n, and using index matching, the nth ranked team can be displayed alongside each position in the league. Goals scored, conceded, difference, wins, draws, losses and points can similarly be displayed. The league table is displayed in real time. This is done without any VBA or SQL programming, and is therefore usable on almost any system without the need for Excel's security settings being triggered.
This is the whole problem your schematic IS a database designed system. You are entering scores which should be a table in a database and the calculations (especially the ranking) should be done DB side. Excel should only be your front end for viewing the data. Doing it all on the DB side means you are free to choose the front end as well; tableau, excel, c#, html, it really doesn't matter what front end you use.