From time to time, you may experience difficulties with Footy Works, be it when installing, registering or running Footy Works. Although Sorensen Technologies has tried to produce the best product possible, there are circumstances that we may not have considered or computer setups that we do not have access to (or we just made a mistake) that may cause users problems in getting Footy Works to function correctly, or even at all.

The following problems have occurred to more than one user, which indicates that these problems are reproducible, and should be easier to fix or work around:

• TIP - When trying to import data, do NOT extract any files from the FWI / ZIP file. Footy Works does this extraction internally. By trying to import the extracted files, the data will be seen as corrupt by Footy Works, so leave them as they were downloaded. If you still have problems importing, try renaming '.ZIP' files to '.FWI'.



• If you are having problems trying to import data, you need to run the Footy Works V1.4.2 Database Data Update. Then update to the latest version of the exe (1.4.2), and then attempt importing the data.
• The 'Most Scoring Shots' statistic under 'Score' currently only returns Home teams - This will be fixed in the next release.
• FIXED - Occasionally a problem accessing the Footy Works database will arise that will cause a run-time error 3420, and will manifest itself whenever Footy Works starts up. If you are a registered user and experience this problem, please contact us for a fix to the program. - THIS HAS BEEN RESOLVED IN VERSION 1.4.1 AND LATER.
• If your system is running low on memory, then some of the large graphs (historical scores, margins and ladder positions for a team) may cause a run-time 480 error. If this occurs, try reducing the number of applications running at the same time, or try viewing just a small range of seasons via the Statistics Season Range area of Footy Works.
• FIXED - Most Goals, Scoring Shots and Behinds under All Matches statistics incorrectly only displays home team results. This will be fixed in the next incremental program update.
• FIXED - Selecting on a specific match-up under statistics matches currently does not display all matches between the two teams. To find this, use the Search facility.
• When entering match results yourself (instead of importing them), you may find that team and opponent average ladder positions are not always correct. You can correct the values manually via the adjust ladder screen.
• When Round 1 matches of a new season are entered, some of the team position values are incorrectly set in the league ladder. These will need to be manually adjusted for the time-being (or import the data from the downloads page).
• When a new season is added but there have been no matches added to it as yet, then if that season is selected in the Search screen, a run-time error will occur if you attempt to perform a search. To prevent this error, do not select the empty season.
• If Footy Works is registered and you wind-back your system clock and then run Footy Works again so that the later run is on an earlier system time than the previous run, Footy Works will unregister itself. You will then need to re-register Footy Works, but before you can do this you must contact us to reset the database first. A fix for this problem will be available shortly.



• TIP - Please note that when upgrading the software, you cannot do this via the import function - you must actually replace the exe file to update the software.
• TIP - When setting your search parameters on the Search screen, please make sure that all the parameters are set to how you expect them to be. Often you may forget that you are search against particular rounds or finals matches etc. from a previous search, and forgetting to reset the parameters for a subsequent search. This can lead to unexpected search results.
• TIP - Many users have confused the Season Range statistics node with the complete statistics node, resulting in the user getting different information to what they were expecting. Please ensure that you are aware of the node that you are currently in before questioning the validity of the results.