View Single Post
Old 05-28-2003, 12:55 PM   #32
Killebrew
Hall Of Famer
 
Killebrew's Avatar
 
Join Date: Dec 2001
Posts: 3,326
UPDATE

Dola posting here:
Quote:
Originally posted by Killebrew
Using the latest version of OOTP History I am getting an "error 94 Invalid use of null" during the generation of a team html page - I believe it is the schedule splits team page.

Background:
I have carefully imported 8 seasons following the instructions in the readme and using the correct CommishJoe programs for the games CSV output. I am attempting to generate all 8 seasons html pages now and the html page generation works well until this error. When the error occurs all the winshares have been calulated, all the player pages have been output, and more than half of the team pages have been generated as well.

The error occurs on the 7th season for a club and the other seasons html for the same club generated perfectly so I know the problem is not that serious, just an issue (expected value is null) with the current year. I have looked in the table with all the year by year game results since that is likely where the team splits html comes from, but's it's difficult to see any problem with that table.

Jeff, any idea of what might be happening here? I can go into further details too if I have missed some stuff, any idea's (from anybody) would be very welcome.
I solved this problem and thought I should update this thread with the reply just in case a similar thing occurs to others and they do a forum search. The problem described above was that a team city name did not get imported for a particular season. The utility was fine with this until it needed to output the team pages from that year, it output part of the team page (the top line or two only) before the app errored out. No idea why the city name was not imported for that one season, it may very well have been a user error when I did team name and location changes. Anyway, if you do a careful check on each of the year by year team screens (via the utility) you can spot an obvious error like this one, and there's no need to get all fancy-like in your troubleshooting.
Killebrew is offline