jainser wrote:WOW

I read all that and let me try to visualise to you what happened in my head.
Large empty space, light wind blowing in from the west and a large lump of bushweed rolling across
Haha

Well, I guess it was a bit "techie speak" - as a database programmer myself, I guess I sometimes fail to remember that not everyone does this kind of thing for a living
jainser wrote:However the last thing I want ot do is load more work on to the guys that all ready have a lot work maitaining our great website.
Would it help if people who have kids just emailed/PM'd there ages/birth year across?
Yes and no.
Yes - it removes the extra data feed, scheduling this job, parsing etc., but the database changes and new page for the Junior Board are still required, so maybe one-third less work to set it up in the first place.
No - the problem then becomes one of maintainability (a concept of fundamental importance to software engineers) - when a new junior member joins the club in the future, JL would have to add their details to the database manually - obviously not ideal.
The advantage of extracting the data from the C2 profiles is that it is all automatic. Once the new code is written, an U19 (or whatever we decide constitutes junior) who joins FS would immediately appear on the junior board as well as the normal one.
Given that the actual amount of work involved is (I think) relatively small, it's probably worth doing 'properly' - getting all of the data (where it can be obtained) from C2.
Max