Bilybob, First of all, I screwed up the table names in my previous post. I got confused with the module that I'm currently working on. Glad to see you were still able to figure it out. Secondly, you probably have found a bug. I think you nailed it on the head when you mentioned that it might have something to do with creating new users mid-season. Since the report is generated on the fly, it builds itself using the Picks table. However, the Picks table is only populated when a) a pick is made, or b) a score is entered for a game (which creates default picks if none exist). So, since you started a season after 3 weeks and didn't make any picks for the first 3 weeks or enter any scores for the first 3 weeks, no pick records were created for the first 3 weeks. If you were starting a brand new pool, the best way would be to add the schedule, add the users, ensure that default picks were disabled and then enter the scores for each game that has already been played. This would populate the picks with 0 points. Once you were up to date with the games, you could enable the default picks again if you wanted to use them with your pool. The best way to fix this might be to put a note in the readme.txt since most users will be starting a pool from the very first week. mike.