News

News Update

Resolving database problems with Golden Records. If you are getting an error message like “A column name is not valid. [node name (if any)=, column name = ” this is because the database has not updated correctly when installing a new version. New features often require an update to the database. This normally happens the

News Update

Golden Records 4.3.16 has been released today. You can now output membership numbers (eg Archery GB numbers) with individual results. An error when searching the archers table has been corrected. http://ow.ly/ji3oi

News Update

Version 2.7.2.2 has been released on 13 February 2013 which resolves the error “{node name (if any)=,Colums name=Active}” caused by the database not being updated by the the program. Anomalies in handicap calculations that caused duplicate and missing handicaps in the handicaps table have also been resolved. A number of issues causing blank reports to

News Update

With Golden Records version 2.7.1.2 released on 7 October 2012 some incorrect classification data was compiled into the program. This has been resolved in version 2.7.1.5 released today 11 October 2012. We apologise for the inconvenience. Users should check scores entered since 7 October.

News Update

Golden Records v2.6.2.3 is now available. This adds the ability to keep archer settings when entering multiple scores from 1 archer. Add Record form has auto-complete functionality. Improvements to classification and handicap calculations.

News Update

Golden Records v2.6 now available.Version 2.6 of Golden Records adds new features and an improved handicap and classification system.In this version the computation of handicaps and classifications is entirely automatic (optional). As scores are entered, the change in the archer’s handicap and classification is calculated and displayed.Scores are now checked against the maximum for the

News Update

Apologies for the inconvenience but the release of Golden Record 2.5.23 last week has been found to contain inaccurate classification data. This has been corrected in verion 2.5.24, and you are advised to update to this version as soon as possible and check any classifications you have allocated since the begiing of April. Once again

BACK TO TOP