RunScore Client/Server Latest Revisions
Note: Revisions are in
fetch the SampleRaces, the Advanced Sample
Races, and the Common directory. The
Common directory contains the latest AgeGrade files, USATF
Performance Guideline (*.TAC) files, and the USA ZIP code file.
These links are provided if you want to fetch the sample races or
common files and don't want to do a complete download.
Keith has documented how to
create a thumb drive that you can give a race director
to type in entries without having to install RunScore on the RD's
RunScore API (Application
Programming Interface) examples: TestRSAPI.zip for use with Microsoft Visual
Studio C++ or C++ Express and testrs.
Documentation on how to
use RunScore with NCAA/DirectAthletics TFRRS-XC: TFRRS-RunScore.pdf.
RSServer/RSClient Version 184.108.40.206 Level 2017.03.18
Ricky Campbell reported that when uploading results that
had no time, the pace displayed as a very large number. This can happen, for
example when uploading a split and a finish time when the runner has not yet
reached the finish line. Fixed.
RSServer/RSClient Version 220.127.116.11 Level 2017.03.02
RSServer/RSClient Version 18.104.22.168 Level 2017.02.08
- Craig Chiger pointed out that if downloaded
registrations from RunSignUp and then imported new registrations from a csv
file, the registration_ids from the initial download were erased. This only
happens if you do not have a registration_id field. Whether you have that
field or not, the registration_ids should show up at the bottom of the
entries screen. Fixed.
- Added new command "List DNF" at suggestion of Tony Newton. When used, if
a participant does not finish a leg of a race, the letters "DNF" are
inserted in the time place instead of leaving the time blank, which is the
RSServer/RSClient Version 22.214.171.124 Level 2017.01.14
- Jenna Ginsbury reported that if an Auto Run/FTP session is running and
the Internet connection is lost. Error messages pop-up. If they are not
cleared, eventually RunScore must be restarted to continue the upload of
files. Fixed by not doing a pop-up message. Instead the error message is
displayed on the Listing Window status line and a beep is issued.
- Dennis Joffe wanted to include information about
whether an entrant was in the club of the sponsoring organization. It turns
out that RunScore was properly processing membership information for USATF
membership and USAT membership but not for the generic club. This is now
handled by putting the membership_id (club id) in a RunScore field. Once
there, you can use a [contro] section in entries.ini to, say, put the club
name in a field or, say, put an X in a field indicating the particpant is a
RSServer/RSClient Version 126.96.36.199 Level 2017.01.06
- Ryan Griessmeyer reported that his video/YouTube
settings were not uploading to RunSignUp. Turns out his results file was a @
file. The reason why this caused a problem is neither interesting nor
informative. Suffice it to say that the problem has been fixed.
RSServer/RSClient Version 188.8.131.52 Level 2016.12.10
- Mike Peabody reported that when sending email, if there
were no entries satisfying the Select criteria, an email got sent to the
last name in the database with the correct Subject and no body. Fixed.
RSServer/RSClient Version 184.108.40.206 Level 2016.12.08
- Carl Magnuson and Jon Krupa were
having problems with RunScore when the MyLaps Toolkit generated a long
location name. It turns out that there was not enough space reserved for a long
- Tim Roman reported that if he switched default printers
with RunScore open, he had to close RunScore and reopen to use the new
default printer. Fixed by Steve Delahunty.
- Mike Peabody reported that Age-Grade percentage was not
rounding the same in Event to Database as in results. The problem was that
the rounding was changed in 2015 as requested by Don Lein,
USATF Long Distance Running Chair. He pointed out that the runner's time
should be rounded to the next second before doing the age-grade percentage
computation. This change was only made in results; not E2D. Fixed.
RSServer/RSClient Version 220.127.116.11 Level 2016.11.28
- Latest stable release
- Steve Delahunty improved times referenced by the MINUS
command so that the command can handle more time formats.
- Made an improvement in Announce so that now you can use the Announce Event feature from RSServer. This allows you to send
e-mail results to a finisher shortly after the finisher crosses the finish
- Craig Chiger was having a problem uploading changed
registrations to RunSignUp. It only happened if the database did not have a
registration_id field (or a field mapped to registration_id) even though it
is not required to have such a field. RunScore keeps track of this. Problem
RSServer/RSClient Version 18.104.22.168 Level 2016.11.04
- Fixed a problem in Team Relay. The same team was
showing up in the header for each team in results.
RSServer/RSClient Version 22.214.171.124 Level 2016.11.02
- Glenn Wolin reported that Division Total
in Announce was not working on the RSClient even though it
was working on RSServer. Fixed.
RSServer/RSClient Version 126.96.36.199 Level 2016.10.30
- Steven Keith found that he couldn't upload native
results to RunSignUp if he had two different categories for one race. For
example, in his race called "5K Run/Walk" he could upload the "5K Walk" but
couldn't upload the "5K Run". He reported that this used to work. With that
as a clue, the problem was found and fixed.
RSServer/RSClient Version 188.8.131.52 Level 2016.10.19
- Lee Stratman reported that some strange characters were
showing up on the results screen when a marker was added to an event in
MyLaps Timing and Scoring. Fixed.
- When Anthony Stroude couldn't get his RunScore E-mail
working through Google or Hotmail, I began a search for a better provider.
Bob Bickel, Founder of RunSignUp, offered
that we could send E-mail under his contract with SendGrid. RunSignUp's
contract allows for very large numbers of e-mails, Bob said we could operate
under their license for free. SendGrid is different from the other e-mail
systems which RunScore supports because it is done through a web API
(Application Programming Interface) rather
than directly to e-mail. We have found it to be very fast and reliable. To
use SendGrid, contact us at
email@example.com to get a userid and password that will give you
access to SendGrid.
- Bill Teschek found that importing a CSV file using Import Replace, did
not replace existing records but created new records. The problem was that
RunScore assumed that the bib number was in the first field. This has been
changed so that the bib number does not have to be in the first field.
- You can now send results e-mail from the Announce screen. However, at
present this only works from RSServer.
RSServer/RSClient Version 184.108.40.206 Level 2016.10.06
- It has always been required that when doing Team Mixed scoring that you
need to set the number of displacers equal to the number of finishers. If
you didn't, the results could be weird. This is now enforced. If you don't
have them the same, you will get a pop-up saying they are not the same and
they will be forced to be the same.
- At request of Brad Pickle, in ZapEvent support, changed
"registration_id" to "participant_id" since the latter is unique; the former
- Mark Iverson was scoring a race which had a team called
"Unalaska". RunScore designated the team members as "Unattached" because all
it was testing was that the first three characters are "UNA". Fixed by
making the test more robust.
- Jon Krupa pointed out that when sending a Json report
(RunScore Results, TFRRS, etc.) to the editor, it is then not possible to
send to the printer without leaving RunScore and coming back in. Fixed.
- When selecting a RaceRoster race, if a race has the
same name for different years, RunScore would often pick the wrong year.
RSServer/RSClient Version 220.127.116.11 Level 2016.09.08
- Jon Krupa pointed out that if you use
Time Format equal to NONE, meaning you don't want that
time to appear, a space occurs in the printed output.
That unwanted space has been removed.
- With cross-country season approaching, the TFRRS sample
races have been added to the update distribution.
RSServer/RSClient Version 18.104.22.168 Level 2016.08.31
- Jenna Ginsburg requested that the lower
logo on an Announce label appear directly under the last
line of print instead of at the bottom of the label.
RSServer/RSClient Version 22.214.171.124 Level 2016.08.20
- Jenna Ginsburg reported that when
printing output from Announce on a label printer, some of
the text is lost if the bottom logo is included. Fixed.
RSServer/RSClient Version 126.96.36.199 Level 2016.08.19
- It was not possible to use the Rate command with a Race
Roster custom report. Fixed.
- Jon Krupa asked that a line of text used
with the ",ce" command be trimmed so that
terminating blanks would not be used in the centering
- At request of Robbie Wilder, the
Tacstats command can now be used in a custom report. For
example, this allows you to report who exceeded the USATF
performance standards or who qualified for the Boston
RSServer/RSClient Version 188.8.131.52 Level 2016.07.20
- When using registration site Race Roster, the events were
not sorting by date as they should. Fixed.
RSServer/RSClient Version 184.108.40.206 Level 2016.07.16
- A bug was introduced in Version 220.127.116.11 Level
2016.07.15 that kept a new race from being
selected when using RunSignUp. Fixed.
RSServer/RSClient Version 18.104.22.168 Level 2016.07.15
- Made a change at request of Bill Teschek
and Steve Delahunty to allow the race
folder to be in a DropBox folder when working with
- A change was made in the RaceRoster
interface allowing a very large number of events. It had
been limited to 50.
- At request of Jenna Ginsburg, make
handling of logos for Announce easier. Now you don't have
to put the logo in the Client folder. RunScore will copy
the logo(s) from RSServer and place it in RSClient.
- Discovered that setting the IP address and TCP from the
command line of RSClient didn't work. Fixed.
- Steve Stone reported that when doing
team scoring on a field and sorting up, the teams sorted
- At request of Steve Delahunty, removed
fix from Version 22.214.171.124 for Bill Teschek to
handle a race folder in DropBox.
- A change to their firewall was made at Active Works that
prevented RunScore from communicating with Active Works.
The problem, however, was not at Active Works but was in
RunScore. That is, a very small one-character change in
RunScore made the problem go away.
RSServer/RSClient Version 126.96.36.199 Level 2016.06.30
- Can now upload custom results to RaceRoster. Operates the
same as with ChronoTrack Live and RunSignUp.
- Increased the number of races that RaceRoster can access.
Was 25; now unlimited.
- Shakeel Noorali pointed out a problem
with the RunScore Open Interface. The incoming string of
data was limited to 30 characters. Made much larger.
RSServer/RSClient Version 188.8.131.52 Level 2016.06.11
- Working with Bill Teschek, changed
location of RSClient temporary files from the race folder
to the RunScore folder. This avoids a problem when the
race folder is in a DropBox folder.
- At request of Jenna Ginsburg, add
support for custom questions when downloading from Active
- Found that when uploading new and modified registrations
to RunSignUp via a listing file, the
last-upload-date-time gets reset so that the next
incremental download downloads all registrations. Fixed.
- Increased the number of events that can be displayed with
RaceRoster from 25 to 100.
RSServer/RSClient Version 184.108.40.206 Level 2016.06.04
- Jim Clark pointed out that the Time
Machine did not work in the "Event(TM)" mode.
That is, if selecting "Event(TM)", the bibs and
times should go into the event as set by the Time Machine
Event. This apparently stopped working when we changed
the Event selection from "Event" to
RSServer/RSClient Version 220.127.116.11 Level 2016.06.01
- With help from Steven Keith, made
improvements in the upload of registrations to RunSignUp.
Is now much more robust.
- Working with Selwyn Blake, have made a
lot of improvements to the Announce feature. You can now
display, in addition to the Division (e.g.DIV or SEX)
Place, Division total which shows the total number of
finishers, who have finished thus far in the specified
- Here is an Announce Screen example generated by Selwyn.
- You can include two logos in a tag printed on a label
printer -- one at the top and one at the bottom. The
logos must be PNG files.
- Here is a Finisher Tag example produced by Selwyn's
- The Announce section in Help has been greatly expanded to
explain the new capabilities.
RSServer/RSClient Version 18.104.22.168 Level 2016.05.21
- At request of RaceRoster, remove
implementation of placeholders when uploading results.
They will manage the fields at their end.
- Steven Keith found that custom questions
in RunSignUp were not uploading from RunScore to
RunSignUp when doing a registration upload. Fixed.
- At request of Selwyn Blake, added Pace
to Announcer screen. He also pointed out that when using
the Message command, sometimes part of those commands
were overwritten by the data on the same line. Fixed.
Also, fixed a number of other small problems with
- At request of Bill Teschek, increase the
levels of Listings file priority from 5 to 9.
- Adam Shelton requested that "Import
replace" be added to the File menu selections.
"Import Replace" is like import but with the
extra feature that if the bib number is the same as a bib
number already in the database, it will replace the
record of the one in the database. Otherwise, it will
append the record as is done with File/Import. This
capability has been present as a command; Adam wanted it
also available as a menu item to make it easier selecting
the file to be imported.
- We are now using a newer version of "Help and
Manual" to produce the help screens. You will notice
small formatting differences.
RSServer/RSClient Version 22.214.171.124 Level 2016.05.11
- At request of Enrique Belchi Ruis, we
have added a new command Pack Time to
assign the time of the leader of a pack to all riders in
the pack in a cycling race.
- The new command Pack Time can also be
used in an Event to Database listing to
insert the Pack Time to a field.
RSServer/RSClient Version 126.96.36.199 Level 2016.04.30
- With testing help from Pedro Zapata,
have added SendinBlue to SMS systems supported by
RunScore. SMS messages through SendinBlue costs only
$0.0134 per text. The complete list of supported SMS
system: BulkSMS, SendinBlue, TextingForward, Twilio,
RSServer/RSClient Version 188.8.131.52 Level 2016.04.26
- Latest stable release
- We used to plug Mandrill
for sending e-mail messages from RunScore. But now
Mandrill, which is owned by MailChimp, is changing their
business model. They are now requiring that you have a
paid MailChimp account in order to use Mandrill. Pedro
Zapata, RunScore customer from Puerto Rico, has
shown us that you can use SendinBlue
just like you used to use Manddrill. It is very easy to
setup. Read the Help section on e-mail. SendinBlue allows
you to send up to 300 free e-mails a day and up to 9,000
a month. If you need to send more, there are
reasonably-priced options available.
- Upgraded to latest version of Help and Manual, the
program we use to generate the Help screens. The only
thing you will notice is a nice looking header at the top
of each topic.
RSServer/RSClient Version 184.108.40.206 Level 2016.04.25
- Steven Keith pointed out that the new
Browse feature (Version 220.127.116.11) was not working in
RSServer/RSClient Version 18.104.22.168 Level 2016.04.24
- Jason Gooding reported that the
"Auto Run" selection does not show up with a
right-click on a listings file name. It turns out, this
was not implemented for ChronoTrack Live, RaceRoster, or
RSServer/RSClient Version 22.214.171.124 Level 2016.04.23
- Andrés Alańón Vázquez from Spain,
reported that RSClient was crashing when first invoked.
We could not reproduce the problem so sent him a special
version with debug statements. Fixed.
RSServer/RSClient Version 126.96.36.199 Level 2016.04.10
- Steven Finkelstein pointed out that a
date field lost its internal format (YYYYMMDD) after
running the "Update All Entries" command. That
particular internal format is uses so that dates sort
properly. Problem fixed. This brought up several issues
debated with Steven and Steven Keith as
to how to do searches on a date field. It used to be that
to search for, say, date-of-birth (DOB) after a certain
date, you had to use the YYYYMMDD format in the command.
Now you can use the date format that the race is using.
- You can use the "Contains" command with a date
field. For example, if you want to find everyone born on
January 15, you would use:
- The BY command, when not used with any
Select commands, produced results in upper case. Also, a BY
on a date field showed the dates in YYYYMMDD format. This
is now changed to show the fields as they appear on your
Enter/Edit screen, e,g, 01/15/2012.
- Liz Dreher pointed out that when
selecting from All races in RunSignUp, the races in the
dialog box are no longer sorted by date. Fixed.
- At request of Steven Keith, make
improvement to Browse. Now if you click on a header field
in order to sort on that field, the same field will be
used for the search feature at the bottom of the screen.
- Pat Leone reported that the total time
in Team Relay was not formatting according to the Time
Format command. Fixed.
RSServer/RSClient Version 188.8.131.52 Level 2016.04.06
- Uploads of results to RunSignUp are now sent in blocks of
500. Before doing this, a very large upload of results
could stall and not run to completion.
RSServer/RSClient Version 184.108.40.206 Level 2016.04.05
- Steven Keith found a problem uploading
multiple results via "Incremental Run". Fixed.
RSServer/RSClient Version 220.127.116.11 Level 2016.04.04
There are a number of significant improvements in this
- Steven Keith helped a lot with
suggestions and testing of the following enhancements.
- Improvements have been made for incremental uploads of
results. You can take a listing file that uploads results
(RunSignUp, ChronoTrack Live, or Race Roster) and turn it
into an incremental upload listings by right-clicking on
it and selecting "Incremental Run". Note that
"Incremental Run" will not work on a @ file.
- A new "Auto Run" feature has been added. Again,
if you right-click on a listing, you will be given a
chance to pick how often the listing file will run. You
can turn "Auto Run" off by selecting the
listing again and turning "Auto Run" off. Note
that this auto run is far easier to turn on and turn off
than the one invoked from within a file.
- People have been asking for years for an auto run that
can handle more than one auto run at a time. This one
- You can have multiple "Incremental Run"
listings running and multiple "Auto Run"
listings running at the same time. "Auto Run"
will work on @ files.
- You could use this capability to have incremental updates
run, say, every 10 seconds and then do a full update
using "Auto Run" every 5 minutes to move any
local changes to the online site.
- At request of Jon Krupa, make an
improvement in mappings for the various registration
sites. If you have a mapping to a field that doesn't
exist in your race setup, that mapping is removed. This
can avoid some problems.
- Fixed a problem in RunSignUp support for how RunScore
handles the event name mapping. Before the fix, there did
not seem to create problems -- just wanted to avoid
- At the request of Selwyn Blake, we have
created a way to send results of @ listings to a file.
This is done by adding two "Super commands",
"Destination" and "Output format"
into @ files. These are not really new commands; it is
just that they can now be used within a @ file to control
the output. Selwyn used these new features to send JSON
output to a file which he then sends to his web site. He
has written code that takes the JSON format and produces
web output. After producing the JSON report, he uses
RunScore's FTP capability to upload to his web site. Here
are two examples that take JSON directly from RunScore to
his site with no involvement by RunSignUp.
Without Team Scoring
Click on "5k Awards" to see
the result of an awards listing producing JSON output
followed by rendering by Selwyn's code.
With Team Scoring
(You'll have to click on the
"Climber Team Awards" to see the team results.)
To show how versatile this capability
is, here is an age-graded team result that I uploaded to
RunSignUp. The JSON is similar in Selwyn's and my reports but
the formatting at the web is very different.
Selwyn has generously offered to share
his code that processes the JSON file. It is written in
HTML5/PHP/JSON as needed. You can contact him at firstname.lastname@example.org.
RSServer/RSClient Version 18.104.22.168 Level 2016.03.14
- Steven Keith had a race where some
RunScore Results (right-click: RunScore Results to -->
Online) were not uploading. Fixed. Also added error
checking to notify a user of problems with RunScore
RSServer/RSClient Version 22.214.171.124 Level 2016.03.11
- Stephen Keith and Craig Chiger reported lots of bogus
errors on uploading to RunSignUp. This only happened in
certain situations. Fixed.
- Made a change to RSClient so that it does not crash (in
most instances) when RSServer shuts down. Makes for easy
restart by just reconnecting when RSServer comes back up.
RSServer/RSClient Version 126.96.36.199 Level 2016.03.04
- Left some under-development copy and paste results menu
items in that have not yet been implemented. Removed.
RSServer/RSClient Version 188.8.131.52 Level 2016.03.03
- At request of Marek Blazek, Czech
Republic, RunScore now supports Unicode data in its
BulkSMS feature. This allows the use of characters with
diacritical marks which are used in many languages.
RSServer/RSClient Version 184.108.40.206 Level 2016.03.01
- Some timers might not like to display negative times (see
Version 220.127.116.11) so it is now an option. The default is
to not show them but to show blanks in place of the
times. If you do want to see negative times, use the
control: "Show Negative Times" in the *.lst
RSServer/RSClient Version 18.104.22.168 Level 2016.03.01
- Working with Steven Keith, have made
changes in the way problems in splits are displayed.
Formerly, if a split ended up with a negative time due to
a bad time or a runner leaving a timing point too soon,
the time was blanked out. Now the time is shown as a
negative time. This gives you more information allowing
you to fix the problem -- or disqualify an individual or
team. The changes are in "normal" listings used
for triathlons and in the Team Relay feature.
- If a time is missing at a timing point, the time will be
displayed as a blank. Not only that, the previous split
and the next split will be blank since the time from that
point is needed to compute the splits. This will pop out
to you allowing you to fix the problem or issue a DQ.
This is not a change but we are listing it here to
highlight the difference between a missing time and an
RSServer/RSClient Version 22.214.171.124 Level 2016.02.23
- At request of Jason Kornetsky, have
added a feature to Live Results so you can place your own
message at the bottom of the screen to replace the
default message of "Results provided by
RunScore." Use "Live Results Msg" command
to compose your own message.
- Improvements have been made to the upload of incremental
results to RunSignUp using RunSignUp's "Native"
methods. That is, this does not use RunScore Results
methods. It just gives you one more way to upload
RSServer/RSClient Version 126.96.36.199 Level 2016.02.21
- Troy Rebert found when downloading team
members from RunSignUp, if all members of a team had the
same bib number, only one member showed up in RunScore.
This was because RunScore assumes that the bib number is
always unique. When it sees a bib number in a downloaded
registration, it checks if that bib number already
exists. If so, it replaces the earlier version of the
registration. But Troy had marked the bib number field to
NOT be unique. A change was made so that RunScore only
does the bib number check if the bib number field is a
RSServer/RSClient Version 188.8.131.52 Level 2016.02.18
- When downloading registrations, sometimes a null
character would get into a field. Normally this is not a
problem but can cause strange behavior when updating
RSServer/RSClient Version 184.108.40.206 Level 2016.02.17
- Support for SMS provider BulkSMS
for texting was implemented at the request of
Marek Blazek from the Czech Republic. Done.
BulkSMS has coverage in most countries. There are now
four SMS providers supported. This support allows you to
send text messages to a finisher seconds after crossing
the finish line. See the SMS section of Help for details.
RSServer/RSClient Version 220.127.116.11 Level 2016.02.15
- Improvements have been made to the uploading of
registrations to RunSignUp feature in Version 18.104.22.168.
- When searching for a given record number in Browse, the
record returned was always off by one. Fixed.
- Chuck Sellers found a problem in
uploading results to RunSignUp. (Not RunScore Results but
"native" results.) Fixed.
RSServer/RSClient Version 22.214.171.124 Level 2016.02.10
- Jim Oaks reported that if he has the
Enter/Edit screen open in RSServer at the same time that
he has one or more RSClients attached and checks on the
attached clients (Misc/Display Active Clients), RSServer
- Steve Stone asked for a new capability
when uploading registrations to RunSignUp. The way it has
been working is if one or more of the registrations has
an error such as an invalid address (e.g. bad ZIP code or
bad state abbreviation), the entire upload is aborted.
The validation is done in RunSignUp. When an error
occurs, RunSignUp reports which records have a problem.
RunScore now uses that information to remove those
records from the upload and uploads the remaining good
RSServer/RSClient Version 126.96.36.199 Level 2016.02.05
- With help from Jon Krupa and Carl
Magnuson, have improved the gathering of gun
times (Markers) from MyLaps Timing and Scoring
application. The gun times are still available from the
- New user Adam Shelton pointed out that a
start time exported has an extra 0.01 seconds added to
each time. Fixed.
- Pat Leone requested a feature to allow
the team position (place) for each finisher. That is,
each finisher can have their team's place next to their
name. This feature is called TEAM POSITION. Also at Pat
Leone's request, the Team Position has been
added to Event To Database.
RSServer/RSClient Version 188.8.131.52 Level 2016.01.31
- Autumn Hayes reported a problem with
RSClient when RSServer and RSClient are on different
computers. It turns out that, very rarely, (one chance in
1024), depending on the total number of characters in all
the file names on the listing screen, the problem can
arise. The source of the problem has been found and fixed
by changing the way the stream of file names are
terminated. Therefore, you must update both RSServer and
RSClient. If you only update RSServer, you will be
presented with an error message when you try to connect
RSClient to RSServer. If this happens, make sure your
RSServer and RSClient at at the same version level. We
appreciate Autumn sending us a failing example so we
could reproduce the problem.
RSServer/RSClient Version 184.108.40.206 Level 2016.01.29
- At request of Steven Keith and a few
others, have added time-of-day to the simulation feature.
You can now specify the time-of-day at which you want the
times to begin. Most chip/tag races use time-of-day
timing so this allows you to simulate more closely the
- At the request of Steven Finkelstein,
have added the capability of downloading teams in
ChronoTrack Live. The team names and other information
will be in a separate database from the team members.
RSServer/RSClient Version 220.127.116.11 Level 2016.01.23
RSServer/RSClient Version 18.104.22.168 Level 2016.01.23
- Steve Stone pointed out that if he
assigned bibs in RunScore, the changed records did not
get flagged as changed so did not get uploaded to
- Changed upload blocksize for RTRT uploads from 2000 to
500 to make the uploads more reliable.
- The ability to concatenate two fields with no space
between them was not working. Fixed.
- Fixed some problems in Race Roster support.
RSServer/RSClient Version 22.214.171.124 Level 2016.01.15
- When opening a file from within RunScore, the file types
*.lst, *.rsm, *.txt are provided. Have added *.ini.
- Made further improvements to RunScore Results.
RSServer/RSClient Version 126.96.36.199 Level 2016.01.14
- Made improvements to RunScore/RunSignUp (RunScore
Results) integration when creating a race from RunScore
and uploading registrations.
- Updated the Sample races with new field "Name"
which is the concatenation of "First Name" and
"Last Name". Makes listing simpler and allows
uploading of "Name" to results as one field.
RSServer/RSClient Version 188.8.131.52 Level 2016.01.11
- Natalie Young pointed out that if she
created a race series in RunSignUp that started in 2015
and finished in 2016, only the 2015 events could be
RSServer/RSClient Version 184.108.40.206 Level 2015.12.11
- Discovered if a person is using the feature to combine
first and last name into a new field, typically called,
"Name", and is also using the Modified Field
capability, all records will be designated as modified
upon an update even if no fields were changed. Fixed.
- Have provided a way to access the test site at RunSignUp
for testing before taking a race "live."
RSServer/RSClient Version 220.127.116.11 Level 2015.12.10
- Have made an improvement that users have been asking for
to the RunScore Results incremental upload capability.
Before you could only designate one file to do
incremental uploads as the race is going. Now you can
have multiple files active. They can all be checking the
same RunScore event or different ones. This is still beta
code so please test before race day before using.
RSServer/RSClient Version 18.104.22.168 Level 2015.11.30
- Version 22.214.171.124 Level 2015.10.28 was
built for the RunSignUp test site. Fixed.
RSServer/RSClient Version 126.96.36.199 Level 2015.10.28
- Pat Leone informed us that Level
2015.10.27 was built for the TFRRS staging site rather
than the production site. Fixed.
RSServer/RSClient Version 188.8.131.52 Level 2015.10.27
- Again no changes have been made to RSServer or RSClient,
but we have updated the TFRRS-XC sample races once more
due to exchanges with Pat Leone, Paul
Vanderheiden, Steven Keith, and the support
staff at TFRRS. This is due to the potential for
duplicate team_code (CODE) names. If you have used TFRRS,
you know there is a CODE field sent to TFRRS with the
field name "team_code". This field is only five
characters long and is created in entries.ini by taking
the first five characters of the School name. It you have
schools like "Western New Mexico" and
"Western State" you will have a problem. To
avoid problems, we suggest:
1. Be sure to score on
"School" (team_name), not on CODE (team_code).
Then you will be passing correct team score information
to TFRRS. That is:
Team Place school
2. Do not upload the team_code. That is, remove or
comment out the lines:
Field Header team_code
To get the new samples, download the SampleRaces.zip from Updates or install the latest update.
In the sample races, CODE (team_code) field is not used. But you might as well keep it around in case you need it in the future.
RSServer/RSClient Version 184.108.40.206 Level 2015.10.26
- No changes made to RSServer or RSClient. Just updated the
TFRRS-XC races due to exchanges between us, Paul
Vanderheiden, and the support staff at
TFRRS/DirectAthletics. The older versions did the team
scoring on the 5-character field CODE which caused a
problem if the school names were the same in the first
five characters. Now scoring is done on the school name
as is done in regular team scoring. References to the
CODE field have been removed from the examples.
RSServer/RSClient Version 220.127.116.11 Level 2015.10.18
- Jon Krupa requested the ability to name
the splits in a TFRRS race. Done. Just use the
"Field Header" command to name the split.
- Added a simpler TFRRS sample race called TFRRSSimple.
This simpler race has no splits and eliminates the
selection on a race. This is not needed and has confused
some user. The selection of the race is done by choosing
the RunScore event. If the races are run as one race,
then you will need to stick with the TFRRSRace so you
separate the runners based on the race number.
RSServer/RSClient Version 18.104.22.168 Level 2015.10.07
RSServer/RSClient Version 22.214.171.124 Level 2015.10.02
- Brian Torres reported that in a
RunSignUp download, the USATF numbers were not
downloading. The memberships had been implemented for the
case when the race had memberships and
this applied to all events within the race. Brian's race
had memberships only for one of the three races. Fixed.
RSServer/RSClient Version 126.96.36.199 Level 2015.10.01
- At request of Sébastien Cadieux, and suggestions
from Jeremy Dill (RTRT.me) made improvements in RTRT
support so large uploads of registrations would work.
Increased the blocksize in uploads from 1000
registrations to 2000 registrations.
- Fixed a problem in the RunScore/RunSignUp
Integration. Was requiring that a database have
a registration_id field but it is not needed since the
registration_ids are kept in an external file: race.ini.
- Jerry Tylutki reported that if two TFRRS
races had the same name, RS might find the wrong one.
RSServer/RSClient Version 188.8.131.52 Level 2015.09.23
- Craig Chiger was having problem
uploading about 4300 registrations to RunSignUp. A change
was made to upload in blocks of 1000 which gives the user
a warm feeling as the blocks upload one by one. However,
this did not solve Craig's problem. It turned out one
person's address had a '&' in the address. This is a
special character for web data amd needed to be
"escaped." That is, it had to be represented as
a hexadecimal character.
- The other problem pointed out by Craig was finding the
offending record when there is a problem such as an
illegal e-mail address (e.g. no @ character or a space in
the address) or a non-existent state abbreviation. A
change was made to pop up all the offending line(s) along
with the statement of the error. This makes correcting
errors much easier. This solution was suggested by Steven
RSServer/RSClient Version 184.108.40.206 Level 2015.09.19
- Level 2015.09.18 was built for the TFRRS staging area
rather than the production area. Fixed.
RSServer/RSClient Version 220.127.116.11 Level 2015.09.18
- Jenna Ginsberg requested the ability to
concatenate two fields together and put them in a third
field but without a space between them. This can now be
done by putting "Space (tab) 0" before the
"Selected Value" commands.
RSServer/RSClient Version 18.104.22.168 Level 2015.09.11
- Tim Roman reported that when he logged
into RunSignUp from RunScore with the wrong login/pw,
instead of the error pop-up, he got a blank pop-up.
- Have added TFRRSTriangularMeet race to
the Sample Races. This race scores team A vs B, B vs C,
and C vs A. You can get the sample races by clicking here
if you download the latest update, the three TFRRS sample
races will be added to your SampleRaces folder.
RSServer/RSClient Version 22.214.171.124 Level 2015.09.07
- New sample race TFRRSDualMeet added to
Sample Races. This is closer to what most people will be
scoring. It contains no splits which makes it easier to
work with. The TFRRSRace has splits.
This new sample race was supplied by Emily Graves.
Both sample races have been cleaned up a lot to remove
- Working with Mike Peabody and Carl
Magnuson (MyLaps) made a change to handle a bib
number being used as a chip ID. The problem is that chip
IDs always filled the field but bib IDs typically do not.
- For TFRRS scoring, you must use the CODE field instead of
the SCHOOL for computing team scoring since this field
can contain UNA (Unattached). When RunScore encounters a
"UNA", it marks that competitor as a non-team
member. This change has been made in the sample TFRRS
- When doing TFRSS scoring make sure you have the
"Team Tie Breaker" set to NCAA. It was not set
earlier in the TFRRSRace sample.
- Fixed a problem in the column format for team scoring.
The report was ending up ragged-right unless you had used
a Squeeze command. The squeeze command is no longer
needed if you are using a NAME field that has the
combined first and last names in it.
RSServer/RSClient Version 126.96.36.199 Level 2015.09.02
- Latest stable version.
- At request of Jon Krupa, sort meets by
date when selecting a TFRRS meet. Also,
allow selection of "All meets" or "Future
RSServer/RSClient Version 188.8.131.52 Level 2015.09.01
- Both Sid Steinweg and Brian
Sparacino reported that they couldn't send a TFRRS-XC
report to the editor. Turns out that neither had obtained
a login/password yet from DirectAthletics.
However, you should be able to produce the report without
having a signon. Fixed.
RSServer/RSClient Version 184.108.40.206 Level 2015.08.28
- Controls for RunScore/Xact integration somehow
disappeared. Pointed out by Debbie Burke.
- At request of Pat Riley, if a problem
pops up while doing an update, either "Update all
entries", F4 or Alt-F4, that pop-up now contains the
offending record number. In addition, if doing Alt-F4, it
pops up the record so you can see the problem.
- Jon Krupa found that if you log into
TFRSS-XC with an incorrect login/password combination,
you would get a response that you were now logged. Fixed.
You will now get an error message that the login and/or
password are incorrect.
- Mike Peabody provided a FinishLynx
(*.LIF) file that would not load properly. The problem
was that the path name had periods in it. The problem
went away when the path was changed to have no periods.
RunScore was fixed so it can now handle periods in a file
- Added information to Help on how to do incremental
results with RunScore Results.
RSServer/RSClient Version 220.127.116.11 Level 2015.08.20
- We are encouraging users to update to this version since
improvements have been made to the RunSignUp integration
with RunScore Results as well as other fixes and
- Fixed a problem that kept the event name field from being
filled in on a download of registrations from RunSignUp.
We appreciate Craig Chiger bringing this
to our attention.
- Download of registrations from imATHLETE
is now officially supported. An earlier beta version only
allowed a download blocksize of 50. Due to a change at
imATHLETE, that is now 1000. We would like some feedback
from RunScore/imATHLETE users.
- Jon Krupa identified a bug which has
been present for many years. If you searched for a
participant in RSClient and it was not found, if you then
entered a new participant it would overwrite record zero
which is the Unregistered Runner Number (URN) on RSServer
even though the user is warned that they are about to
overwrite it.. With Jon describing how to replicate the
problem, it has now been fixed.
- Fixed TFRSS-XC problem identified by Clyde
Resendez. Disqualified persons were showing up
with a team score. Craig Wilson provided
an example with some incomplete teams that produced the
wrong team results ordering.
- Was requiring parameter "meet_id" in TFRSS-XC
header but now supply it from selected meet.
This change is reflected in the sample TFRRS race in
- The download for this update now includes the Sample
- At request of Brian Sparacino, add baud
of 115200 to the external timers table. He is using a new
Trident chip set that supports this baud.
RSServer/RSClient Version 18.104.22.168 Level 2015.07.21
- Version 22.214.171.124 Level 2015.07.15 was inadvertantly
uploaded with test code. If you were unable to log into
your account, download and install this version.
RSServer/RSClient Version 126.96.36.199 Level 2015.07.15
- The fix in Version 188.8.131.52 for handling a double quote
within a field caused the last field in a CSV import to
not be processed. Pointed out by Mark Toretsky. Fixed.
- Have included the TFRRSRace in the
update download. The NCAA is working
with DirectAthletics and have developed
this required format for all college cross-county meets
starting this fall. It will probably also be used for
many high school race. We are looking for testers.
RSServer/RSClient Version 184.108.40.206 Level 2015.07.14
- Debbie Burke reported that the
single-line header for each team on team results uploaded
to ChronoTrack Live, did not render properly. With help
from Bob Lyons, ChronoTrack Live,
problem was fixed.
- Active Works no longer requires a timer
to contact their Active representative for an app token.
The new procedure is: "For a Timer to view an
Events data, an Event Organizer
must invite them. When individuals
accept an invitation to be a Timer in the system,
ActiveWorks Endurance now automatically checks if they
have an API token. If not, the system will automatically
email the token to them. Additionally, Event Owners and
Timers can email themselves an API token by
clicking Get Timing API Token on the
RSServer/RSClient Version 220.127.116.11 Level 2015.07.13
- Craig Chiger had problems uploading
registrations to RunSignUp. The root of the problem was
that the RunSignUp event_id was not getting populated on
download of registrations. Craig was using event_id
rather than event_name.
- Jenna Ginsberg and Jon Krupa pointed
out that on import or export, RunScore was not handling a
double quote (") within a field. Fixed.
- Chad Croucher reported that the
date-of-birth was not formatting correctly upon a
download from RunSignUp. The problem was that he didn't
have the DOB field flagged (in Design Screen) as a date
field. To avoid these problems, now RunScore forces the
DOB field (as designated in entries.ini) as a date field.
RSServer/RSClient Version 18.104.22.168 Level 2015.06.23
- Working with Clyde Resendez, have
improved the TFRRS-XC reporting. You can
now designate DNF, DQ, or DNS in a specified field. If
this field has data, that person is removed from the
finisher order and appended to the bottom of the results
with no time or place and the DNF, DQ, or DNS
designation. Details on how to upload TFRRX-XC
reports are in the help screens.
RSServer/RSClient Version 22.214.171.124 Level 2015.06.17
- Uploading RunScore Results to RunSignUp uses the
reg_id.txt file in the race folder to store the
registration_id values. A registration_id field is not
needed. If it IS used, the results were getting the
registration_id from the reg_id.txt file which could
cause a problem if the id is in the field and not the
file. Made a change so that RunScore now checks for the
registration_id in both locations.
- Mark Toretsky and Steven Keith
reported that a race simulation caused the first person
in the race to be a non-runner, that is, someone without
a bib number. The problem was introduced in 2014 when the
simulation was changed so to not include the unregistered
runner number. Fixed.
RSServer/RSClient Version 126.96.36.199 Level 2015.06.16
- Chad Croucher reported that RunScore
crashed after making a change in the Design Screen and
attempting to save the change. It turns out he had a
field with no label. A change was made to post an error
message when this happened. You must fix the problem
RSServer/RSClient Version 188.8.131.52 Level 2015.06.15
- An incremental download in RunSignUp was downloading all
registrations because the time stamp of the last download
was not getting updated. Fixed.
RSServer/RSClient Version 184.108.40.206 Level 2015.06.14
- With both ChronoTrack Live and RunSignUp, if a user did
an upload of new and changed registrations, the program
assumed that an earlier full upload had been done
earlier. That is not longer required. Pointed out by Bill
- Scott Muir provided us with a race in
which RSClient always crashed when connected to RSServer.
Protection in RSServer against a certain condition had
not been also been used in RSClient. Fixed.
RSServer/RSClient Version 220.127.116.11 Level 2015.06.08
- Was including 2015 Age-Grade files in updates but they
were not included in last few updates. Pointed out by Patrick
Lynskey. They are included again in this update.
RSServer/RSClient Version 18.104.22.168 Level 2015.05.26
- Ryan Walsh reported that the changes to
Announce worked in RSServer and RSClient. Turns out I
forgot to rebuild RSClient. Done now.
RSServer/RSClient Version 22.214.171.124 Level 2015.05.24
- Ryan Walsh, in using the Announce
capability for a lap race, couldn't get Average Lap Time
and Last Lap Time working. Fixed.
RSServer/RSClient Version 126.96.36.199 Level 2015.05.22
- Jon Krupa reported that the command
"Contains" was not working for him. It turns
out it was only working if what you are comparing is all
upper case. It is fixed so you don't have to use upper
case characters in the string you are comparing.
- Bill Teschek reported that the upload of
changed records to ChronoTrack Live uploaded the same
records each time. Fixed. Note: if fields such as the
age-division field, often called DIV, changes, that does
not result in that record uploading. The record is only
flagged as changed if the field changed is one of those
fields that are to be uploaded. To find out which fields
they are, look in the CTLive_fields_mapping.ini file in
the RunScore folder. The same is true when uploading
changed records to RunSignUp.
RSServer/RSClient Version 188.8.131.52 Level 2015.05.18
- Jeff Fedorko requested that the time
format control work for Team Relays. Fixed.
- Sébastien Cadieux reported that Version 8 will
not run on Windows XP systems. Fixed.
RSServer/RSClient Version 184.108.40.206 Level 2015.05.13
- At request of Doug Liverside, extend the
number of parameters from 20 to 36 (1 -10, 'a' - 'z').
Had been implemented only as far as 'j'.
- At request of Gillian Bedrosian, remove
pop-up when an export contains no entries. Preserve
pop-up when export is part of an upload of registrations
RSServer/RSClient Version 220.127.116.11 Level 2015.05.10
- Fixed a problem that required you to have a [data]
section ending every [contro] section. That is no longer
- Doug Liverside reported a problem with a
right-justified field not justifying the result of a
"Selected" operation which made subsequent
searches not work properly. Fixed.
- Dave Henry reported that if you used the
keypad feature in Announce. RunScore would crash. It
turns out the keypad module never got moved over from
Version 7. Fixed.
RSServer/RSClient Version 18.104.22.168 Level 2015.05.02
- In version 22.214.171.124, made a mistake in the Online
selection so that selecting RunSignUp as the online
system brought up the wrong system. Fixed. Reported by Craig
RSServer/RSClient Version 126.96.36.199 Level 2015.04.30
- Fixed another problem with ActiveWorks pointed out by Craig
- Added two features to Announce for use with lap races,
requested by Andrés Alańón Vázquez:
"lap distance field" for keeping the lap
distance in a field. This is for races where everyone is
not running the same distance. Likewise, added "laps
left field" to specify the number of laps and to
tell Announce to display the number of laps left when
everyone is not running the same number of laps.
- The reason this release moved from 188.8.131.52 to 184.108.40.206 is
that the new Announce features requires that RSServer and
RSClient be at the same level.
RSServer/RSClient Version 220.127.116.11 Level 2015.04.29
- Craig Chiger found a problem with the
ActiveWorks support if you don't have an Event field.
RSServer/RSClient Version 18.104.22.168 Level 2015.04.28
This version is a merge of RunScore Results, Version
22.214.171.124 and RunScore Version
126.96.36.199 to create RunScore Version 188.8.131.52.
What does this mean? It means that from now on, whenever you
use RunScore to interact with the RunSignUp site, you will be
using the RunScore Results. Also, uploading and downloading
registrations at both RunSignUp and ChronoTrack Live have gotten
easier. We eliminated "Sync with server" and replaced
it with a very easy way to download changes from the system and
upload changes made in RunScore to the system.
The RSRServer and RSRClient (RunScore Results server and
client) have been retired. The new modules have the same name as
the old ones. If you think you may want to go back to Version
184.108.40.206, save it. Or you can do a complete download using
RunScoreSetup.exe to revert to 220.127.116.11.
View the short video on the main RunScore page: www.runscore.com which
highlights features of this new integration. Also on the main
page is a document showing how to allow each runner to see
themselves crossing the finish line on a YouTube video.
- You no longer need to have a field
"registration_id" in your database. The
registration_id information is kept in a separate file
(race.ini) in the race folder.
- Also in the race.ini file are time stamps for each record
that has been changed. This is used for upload of changed
- "Sync with server" has been removed due to
problems. In its place you can do an "Incremental
download" to get changed online records. Likewise,
you can upload new and changed RunScore records with one
click. This works for both ChronoTrack Live
- You can take advantage of these features without making
changes to your normal RunScore setup.
- Results are extremely easy to post. You merely right
click on a listing button and instead of sending to a
printer or the editor, you send it online. Handles
overall results, award listing, and team results. With
one more click you can view the results online.
- Set up for e-mail and text notifications. Once set, a
runner or his friends can go to the RunSignUp site and
ask for e-mail and/or text messages for selected runners.
- Provide links for each finisher to the specific person in
a YouTube video showing that person
finishing. This is all done from RunScore.
- You can download from RunSignUp to get the participants
or, if you have another way to obtain participants you
can put them in RunScore and with one click upload them
- Not using the RunSignUp site for registrations for this
race? You can still take advantage of the above features.
There is a nominal cost for posting results. There is
also a cost for text messages. If you ARE using RunSignUp
for registrations, these services are free.
RSServer/RSClient Version 18.104.22.168 Level 2015.03.31
- Steven Keith pointed out "Modified
Field" was not working in RSClient. Also got
"Contains" working in RSClient.
RSServer/RSClient Version 22.214.171.124 Level 2015.03.30
- Fixed a problem with upload of registrations to
RunSignUp. If the unregistered runner number is included
(usually by accident) in the upload, the registration_id
can be assigned to the wrong entry.
- At request of Steven Keith, have added a
new control "Contains" which test if a field
contains a given string of characters.
RSServer/RSClient Version 126.96.36.199 Level 2015.03.27
- Fixed a problem reported by Craig Chiger about a problem
in downloading registrations from RunSignUp.
RSServer/RSClient Version 188.8.131.52 Level 2015.03.26
- At the request of Jenna Ginsberg, have
extended the Total (to a field) command to handle times.
The receiving field must be flagged as a time field.
- Craig Chiger reported that when
downloading from ActiveWorks, that all of the
date-of-birth fields had the same date. Fixed.
RSServer/RSClient Version 184.108.40.206 Level 2015.03.17
- Debbie Burke reported a problem
downloading, internal to RunScore, registrations from
ChronoTrack Live. It turns out the CSV file had embedded
JSON data describing transactions. These data are usually
not needed for timers so Bob Lyons,
ChronoTrack Live, provided a way to eliminate the JSON.
RunScore Results: RSRServer/RSRClient
Version 220.127.116.11 Level 2015.02.12
- No longer available. Merged into RSServer. See above.
RSServer/RSClient Version 18.104.22.168 Level 2015.03.10
- Doug Cleavenger reported that CSV files that had
line-feeds within a field did not import correctly.
RSServer/RSClient Version 22.214.171.124 Level 2015.02.23
- Latest stable release.
- Add "Modied field" to RSClient. It doesn't do
anything but it keeps an error message from popping up.
RSServer/RSClient Version 126.96.36.199 Level 2015.02.18
- The "Modified field" (see Version 188.8.131.52) now
gets a time stamp on a download of registations and upon
running "Assign numbers".
RSServer/RSClient Version 184.108.40.206 Level 2015.02.16
- Working with Steve Stone, Best Times,
and Jeremy Dill, RTRT.me (Real-Time
Runner Tracking) we have the RunScore/RTRT
integration working. You can download registrations from
a registration site and upload these to RTRT for runner
tracking. When you make changes in RunScore, they can
immediately be uploaded to RTRT.
- Added a new control to entries.ini. "Modified
field". This field must be at least 19
characters long to receive a time stamp in the format:
YYYY-MM-DD HH:MM:SS. The field is populated with the time
stamp if a change is made when updating (F4, F10, F12, or
- Fixed some problems in the RunScore Open Interface for
bringing chip or tag data from systems that are not
supported by RunScore.
RSServer/RSClient Version 220.127.116.11 Level 2015.02.12
- Fixed a problem in ActiveWorks support pointed out by Steven
Keith. If your credentials are wrong, you don't
get the proper message. Fixed.
- At request of Gillian Bedrosian added a
new control "Sort blanks last" that puts any
blank fields at the end of the sorted list. When sorting
on multiple fields, you can have some sort blanks last
and some sort with blanks first. This is handy for
listing results of triathons where there may be no
results for some people on a few events.
RSServer/RSClient Version 18.104.22.168 Level 2015.02.10
- Scott Langford reported since adding the
mixed team average time scoring, a '(' appeared on the
header of each team. Fixed.
- Have added RaceEntry
to registration systems supported. To use ActiveWorks,
you must obtain an application token for RunScore from
your ActiveWorks representative.
(Real Time Runner Tracking) is now supported.
- Matthew Studholme reported that
"Sync with server" not working correctly with
- Matthew Studholme reported that
date-of-birth not uploading under
- The age-grade tables have been updated
to the new 2015 tables. These have been approved by the USATF
and World Masters Athletics (WMA). These
tables are included in a download of the update. I
upgraded the tables last fall after the new world
Marathon record made me take a look at the 2010 (female)
and 2004 (male) tables and decided they needed to be
updated with all of the new single-age bests. One of the
on-line age-grade calculators is using the new tables
RSServer/RSClient Version 22.214.171.124 Level 2015.02.05
- Fixed a problem reported by Jenna Ginsberg
in "Team Place" based on a field. She had very
large numbers in the fields.
- Fixed another problem reported by Jenna
in "Instant Results" caused by field length
longer than the inherent field length.
RSServer/RSClient Version 126.96.36.199 Level 2015.02.02
- At request of Troy Rebert, added
capability to send Team Relay output to an
- At request of Jenna Ginsberg, extended
the "Total" command to allow totals to be put
into database fields. This is handy for putting the team
total points into a field for everyone on that team. This
is controlled by adding a "Database Field"
command which indicates which field should receive the
RSServer/RSClient Version 188.8.131.52 Level 2015.01.23
- In March 2013 the use team scoring by average time with
mixed-team scoring was no longer allowed because
average-scoring used ALL finishers. Now, due to a request
by Scott Langford, this restriction has
been removed. When using mixed-team scoring, only the
number of finishers specified in "Team Score"
- The computation of age-grade percentage has been changed
to use the rounded-up time before computing the
percentage. This is the standard method which RunScore
was not following.
RSServer/RSClient Version 184.108.40.206 Level 2015.01.11
This will be handy in RunScore Results when you want to upload
the full name instead of First Name and Last Name.
- At request of Jason Kornetsky, restore
the AMB Pro Chip support by creating a more robust test.
This will keep it from being confused with the MyLaps
prochip format coming through the Toolkit.
RSServer/RSClient Version 220.127.116.11 Level 2014.11.19
- Fixed a problem Steven Finkelstein was
having uploading and downloading using ChronoTrack Live.
He called his entry_id field CHRONO_ID to make it the
same as that field at the CTLive web site. There's
nothing wrong in doing that but RunScore did not handle
- ZapEvent can now list "Future
events" and "All events". Previously, it
just listed future events. Problem pointed out by Brad
- Jon Krupa pointed out that if you modify
a listing file and, without saving it, quit RunScore and
after answering that it is okay to quit, you get the
pop-up asking if you want to save the modified file. If
you click "Cancel" on that pop-up, your system
and custom variables from Entries.ini will be messed up.
RSServer/RSClient Version 18.104.22.168 Level 2014.11.08
- Have integrated RunScore and the registration sites of SignMeUp
We're looking for some testers.
RSServer/RSClient Version 22.214.171.124 Level 2014.11.05
- At suggestion of Debbie Burke, allow the
selection of "All events" or "Future
Events" for ChronoTrack Live. And following a
suggestion by Steven Keith we put
"Future events" as first item on menu rather
than second. Did the same for other registration sites
that allow you to select all or future events/races.
RSServer/RSClient Version 126.96.36.199 Level 2014.11.02
- Greg McCormick provided an example of an
external/custom results report not working. Found his
database had some illegal characters. Made a change so
that such characters will not cause a problem in the
future. Also, fixed a problem that caused an incorrect
date to occur in the data being sent to the server.
RSServer/RSClient Version 188.8.131.52 Level 2014.10.27
- Formerly which registration system you are using was
saved in the Windows Registry. Steven Keith
requested a change to save which system in the race
folder since usually different races use different
systems. He said he would switch to a different race and
forget to switch the system. The change has been
- Bill Teschek was having trouble
uploading registrations to ChronoTrack Live. The problem
has been fixed. In addition, the feature that informs you
about any upload errors has been improved.
RSServer/RSClient Version 184.108.40.206 Level 2014.10.25
- Natalie Young identified a problem with
"Sync with server" for online systems. This
occurred when the mapping file was moved from the
RunScore folder to the race folder. The appropriate
changes were not made for the "Sync with
server." This did not affect "Sync with
server" for ChronoTrack since that mapping file
remains in the RunScore folder.
RSServer/RSClient Version 220.127.116.11 Level 2014.10.03
- Richard Secrest reported that the NK
2000 stop watch was not importing the times.
Neilsen-Kellerman sent us a loaner watch which allowed
ust to fix the problem.
RSServer/RSClient Version 18.104.22.168 Level 2014.09.26
- At request of Pierre Canton, Sportstats,
have added Divide and Divide By
commands which work like the Multiply
and Multiply By commands except they
divide instead of multiply. He wanted it to compute the
average lap time by dividing the total time by the number
RSServer/RSClient Version 22.214.171.124 Level 2014.09.18
- Brad Pickle found that doing an
incremental download by activity from a ZapEvent event
did not fetch all the new registrations. Fixed.
RSServer/RSClient Version 126.96.36.199 Level 2014.09.16
- Brad Pickle had problems downloading a
race from ZapEvent when one of the fields was so long it
wrapped into the next record. Fixed.
RSServer/RSClient Version 188.8.131.52 Level 2014.09.10
- Greg McFerren reported a problem if you
use a very large listing file for Announce on RSClient.
RSServer/RSClient Version 184.108.40.206 Level 2014.09.06
- Craig Wilson reported that the
Destination command, when sending to a TCP/IP host, did
not work. Fixed.
RSServer/RSClient Version 220.127.116.11 Level 2014.08.27
- Greg McCormik reported that an external
cross-country report to RunSignUp did not work. If he
took out the team place it worked. This clue gave us the
information needed to find and fix the problem.
- David Leatherman reported a problem when
using the Left Margin command along with a null record
- Dusan Kafka reported that Live Results
with custom headers works fine on RSServer but not on
RSServer/RSClient Version 18.104.22.168 Level 2014.07.14
- Latest stable release
- At request of Brad Pickle and Jake
Krohn (Pickle Events), you can now download
registrations from ZapEvent by Activity or you can select
to download all activities. This is now the same as it is
for ChronoTrack Live and RunSignUp.
- A change was made in Eventbrite on how a ticket_id
(usually mapped to an event in RunScore) is handled.
RunScore made a change to accommodate it.
RSServer/RSClient Version 22.214.171.124 Level 2014.06.24
- Added capability to download bib numbers (which they call
assigned_number) from registration site Eventbrite. Brian
Hoover has been very helpful in debugging the
- Implement "RunScore Open" interface so that new
chip/bib systems can transmit data to RunScore without
RunScore having to support each new system. See Help for
RSServer/RSClient Version 126.96.36.199 Level 2014.06.18
- Andrew Sbertoli and Jim Brimm
pointed out a strange problem that occurred when they
connected RSClient to RSServer. The search fields in the
results screen sometimes got scrambled. It turned out
that this only happened if some of the fields in the race
setup had a search field length different than the field
length. These days most timers keep these lengths the
same so do not see the problem. The search field was
established back in the DOS days to conserve memory. It's
not as needed these days. Although, one reason for
setting the search field length shorter than the field
length is to be able to see more search fields in the
Results screen. The problem has been fixed.
- Jenna Ginsberg pointed out that when she
uses the left margin command to move the output over, the
footer gets moved but the header does not. Fixed.
RSServer/RSClient Version 188.8.131.52 Level 2014.06.15
- Steve Gajerski pointed out a problem
that sometimes made a Select command act
like a Select Event command. Fixed.
- Jon Krupa pointed out a problem when
doing team age-grading when he put the Event command
after the Team commands. Now if you do that, you receive
a warning. If this happens, just put the Event command
before the Team commands.
- Jon Krupa also pointed out a problem
where, in team scoring, sometimes the header is
replicated at the bottom of the first page. Fixed.
RSServer/RSClient Version 184.108.40.206 Level 2014.06.10
- Add new capability to Eventbrite so that
if you obtain authorization for a the timer's site on one
computer, there is now a way to copy the credentials to
RSServer/RSClient Version 220.127.116.11 Level 2014.06.09
- Added support for registration site Eventbrite
- Craig Chiger and James Orr
reported a problem with Version 18.104.22.168 when downloading
from RunSignUp if the entrants had previously been
downloaded by an earlier version. Fixed.
RSServer/RSClient Version 22.214.171.124 Level 2014.05.29
- After several requests you can now download selected
events (RunSignUp) or races (ChronoTrack Live) or, as
before, download all. The Sync With Server
has been enhanced so that the synchronization is done
just with the events or races that you last downloaded --
even if that download was during a previous session.
- When recent changes were made to Announce, the
records/page was not handled properly. If you didn't set
Records/Page to a value, the default value became two. If
you did set Records/Page, it worked okay. This has been
fixed so that the default is now 31.
- Andrés Alańón Vázquez reported
problems with the new Announce. He wanted narrower
columns when using his own defined header so that he can
put more information on a line for his lap races. If
RunScore generates the headers, the column widths are
larger so that the entire header is displayed. If you
want to control the column widths, use "Header
Length" after each item such as "Laps
RSServer/RSClient Version 126.96.36.199 Level 2014.05.10
- Sid Steinweg sent us a race that caused
problems if he ran Live Results on RSClient before doing
a listing on RSServer. Live Results wasn't the problem,
it was there were fields that were not search fields but
were used in the listing as search fields. Therefore,
RSClient made them search fields but RSServer did not.
This might fix some of the search field problems that
people have been having but we're not sure.
- Brad Pickle sent an example in which
RSClient would crash when first invoked. The problem was
that enhanced processing of entries.ini had been added to
RSServer recently but the same change had not been put in
RSClient. When that was done, the problem went away.
RSServer/RSClient Version 188.8.131.52 Level 2014.05.05
- John Luaces reported that age-grading
didn't work unless the "Age Field" and
"Sec Field" commands are in entries.ini. Fixed.
RSServer/RSClient Version 184.108.40.206 Level 2014.04.30
- Have added a new command "Import Replace"
to be used in a listing file. When a record is read it,
it checks to see if a record with that bib number already
exists. If it does, it replaces the old record. If it
does not, it appends the record in the usual way. This
feature can be used to fill in later the entrant data
when runners with no registration data cross the finish
- Tim Roman provided an example of the new
color text feature not working correctly in Annouce if he
used the "Announce Update Sec" feature. Fixed.
RSServer/RSClient Version 220.127.116.11 Level 2014.04.27
- Brad Pickle reported that the newly
revised Announce screen had some problems with one of his
applications. Fixed. Also, Text Color wasn't working
correctly. This was also fixed.
- At suggestion of Steven Keith provide a
way to process an arbitrary *.ini file with commands that
are in the entries.ini file. In this way, you can write a
new *.ini file and process it without it remaining in the
entries.ini. The syntax, in a *.lst file, is:
"Process INI File (tab) filename.ini".
RSServer/RSClient Version 18.104.22.168 Level 2014.04.18
- Made some improvements to the feature of uploading
external reports to RunSignUp or ChronoTrack Live.
- Added videos to www.runscore.com
to show how easy it is to upload to RunSignUp and
RSServer/RSClient Version 22.214.171.124 Level 2014.04.17
- When importing times into a start event, use the slowest
time for each bib number; when importing into a finish or
split event, use the fastest time.
- At request of Steven Keith and
Brad Pickle, change the way the
fields_mapping.ini file is used. It used to put it in the
RunScore folder so that it was available to all races. A
race-specific copy is now put in the race folder but a
master copy is maintained in the RunScore folder so
that other races can use it. The logic for the change is
to have all the master mapping for the online systems
regular fields, in the RunScore folder, but have a
race-specific version, with race-specific questions
included, created and used in the race folder, so that it
can be shared from machine to machine. RunScore will
ensure that a copy resides in both places when you first
create the mapping on a new race or machine. This change
is for RunSignUp, ZapEvents, and EpicSignUp. No changes
have been made for RaceIt or ChronoTrack Live. We might
make similar changes for those systems if people request
RSServer/RSClient Version 126.96.36.199 Level 2014.04.11
- Steven Keith pointed out that sending an
"External Report" to a results site was posting
only the last page of a multi-page report. Fixed.
RSServer/RSClient Version 188.8.131.52 Level 2014.04.10
- Pedro Zapata send me a race that had new
MyLaps BibTags that had a hyphen between the Group ID and
the bib number which made RunScore "think" it
was an AMB Elite Chip. Removed AMB from RunScore
temporarily until we can resolve this.
- Andrés Alańón Vázquez reported that
chips were no longer being read in RSClient. Fixed.
- Steven Keith reported a problem with an
age graded report. The problem was nothing he was doing
wrong but the way some of the commands were being handled
in entries.ini: Date Format and Age
- Have added support for EpicSignUp
- When putting external results reports online with
RunSignUp or ChronoTrack Live, you now do it from
right_click "Output to Online system" instead
of enabling it from the Online menu item. This prevents
problems of enabling and forgetting it is enabled and
sending reports that you don't want online.
RSServer/RSClient Version 184.108.40.206 Level 2014.04.04
- Brad Pickle reported that download from
ZapEvent had stopped working. Fixed.
RSServer/RSClient Version 220.127.116.11 Level 2014.04.02
- Richard Rostant reported that printing
from the Announce screen only printed time and not any of
the other information. It worked fine if no event were
specified. Within an hour Mike Marion the
same symptom but with sending text messages. A bug was
introduced with a recent change to the Announce feature.
Fixed for both cases.
RSServer/RSClient Version 18.104.22.168 Level 2014.03.28
- Andrés Alańón Vázquez pointed out a
few more problems with the Announce feature. Columns were
not lining up with headers. Fixed.
- Support added for External Report for
team scoring by time. This means that to upload a team
score to RunSignUp or ChronoTrack Live, all one has to do
is select "Put results online" and then process
the report again.
RSServer/RSClient Version 22.214.171.124 Level 2014.03.19
- At request of James Orr, implemented External
Report for Team Score. At present, this just
works for team score by cross-country rules and column
format. Also, added a new menu item for RunSignUp:
"View external report online".
- Jenna Ginsberg reported that centered
lines in a footer were not centering. Fixed.
- Jenna Ginsberg also requested that Team
Score Export be supported for team scoring by
time. It previously had been supported only for
- Andrés Alańón Vázquez provided us
with an example of Announce failing in RSClient and
causing a crash. Fixed. He was scoring a marathon on a
track and had created an Announce screen keeping the
runners informed on their laps, time, and distance.
RSServer/RSClient Version 126.96.36.199 Level 2014.03.11
- Mark Hendley reported that the
"Triple Cities RC" external device stopped
RSServer/RSClient Version 188.8.131.52 Level 2014.03.03
- Mark Toretsky found that a blank
character was getting into his authorization string tor
Twilio SMS. Fixed.
- The menu items Tools and Online disappeared when in text
editor mode. Fixed.
RSServer/RSClient Version 184.108.40.206 Level 2014.03.01
- Latest stable version
- When downloading from RunSignUp or ChronoTrack Live,
people have complained that if they do a download on top
of an older download, any new data such as bib numbers
are wiped out. This is changed now so that if a
downloaded field is blank, it will not write into the
equivalent field in RunScore.
- When the Online menu item was added, Help on the menu bar
disappeared. It has now reappeared.
RSServer/RSClient Version 220.127.116.11 Level 2014.02.27
- In the change for Carl Magnuson in
Version 18.104.22.168 regarding empty comma-separated fields in
entries.ini, a bug was introduced that caused selection
problems in space-separated fields in entries.ini. Fixed.
- Steve Stone reported that the
"Message" command in an Announce Screen was
overwriting race data. Fixed.
- Andrés Alańón Vázquez reported that
European style dates (dd/mm/yyyy) were not being handled
properly in export and import. Fixed.
- You can now select on a date field as if it is in
YYYYMMDD format even though it might be in MMDDYY format.
For example, a select on the field asking for all
entrants who have a date-of-birth later than 1990, you
would have a select with the condition: "GT (tab)
RSServer/RSClient Version 22.214.171.124 Level 2014.02.11
- Fixed problem with SMS for both UpcellText and Twilio as
reported by Mark Toretsky (UpcellText)
and Andrés Alańón Vázquez, (Twilio).
RSServer/RSClient Version 126.96.36.199 Level 2014.02.09
- At request of Andrés Alańón Vázquez,
add a prefix capability to SMS messaging. Often the
mobile phone number is the base number but, particularly
in countries outside of the US and Canada, a '+"
plus a country code must prefix the number. To implement
this feature, add a new field in your RunScore database
called, say, "Mobile prefix". Then in
entries.ini tell RunScore the name of this field using
the new SMS Prefix Field command, e.g.
- SMS Prefix field (tab) Mobile prefix
RSServer/RSClient Version 188.8.131.52 Level 2014.02.08
- James Orr reported a problem with Live
Results running on RSClient. Fixed.
RSServer/RSClient Version 184.108.40.206 Level 2014.02.06
- The method for selecting which online systems RunScore is
connecting to has been changed to make things easier to
use. Now, you first go to Tools/Online System to
select the system (Active, ChronoTrack Live, RaceIt,
RunSignUp, RTRT, Texting, XACT, ZapEvent). You can go to
Online where, instead of seeing submenus for each system,
you will have only the submenu for the online system you
selected. This helps avoid the problem some are having of
clicking on the wrong system.
- Documentation has been added in the Help files for
integration of RunScore and the Xact system.
- Fixed some problems with Version 220.127.116.11 and 18.104.22.168.
RSServer/RSClient Version 22.214.171.124 Level 2014.02.02
- Carl Magnuson pointed out that if there
are empty fields in a CSV file being used in entries.ini,
that the data did not get parsed correctly. Fixed.
RSServer/RSClient Version 126.96.36.199 Level 2014.01.31
- RunSignUp support now includes a menu check item to put
an "External Report" online. An "External
Report" is a normal RunScore report that is rendered
in JSON which RunSignUp transforms into online results.
- The documentation in Help for uploading RunScore Results
has been completely rewritten with many examples.
RSServer/RSClient Version 188.8.131.52 Level 2014.01.29
- At request of Jenna Ginsberg add to
Export of times:
- Control of time format
- Pace and Rate
- Field Header for Pace and Rate
- Also at request of Jenna, add to Live
- Column headers for Rate and Pace
- At request of Robert Youngs, make
"Field Header" command work in Live Results so
that you can put your own column heading on each column.
- Gillian Bedrosian. Sportstats, Canada
has a very complicated @ listing file designed to produce
some impressive html. However, an error pops since
RunScore was not letting an entire lengthly line to be
read in. Fixed.
- Note: the improvements to Export allow much simpler
uploads to RunSignUp. See the section on RunSignUp for
RSServer/RSClient Version 184.108.40.206 Level 2014.01.27
- Bill Rozen pointed out that the
"Announce Event" feature was not working.
RSServer/RSClient Version 220.127.116.11 Level 2014.01.26
- Troy Rebert reported that the changes to
Announce caused the "Announce Header" mode to
not start each line on a new line as it had before.
- Also fixed a few more things in the Announce feature.
- John Luaces reported that when importing
times, if those times contained bib numbers of zero, only
one showed up. The change on 2013.11.30 concerning import
of times did not take into account that a unregistered
runner number should not be replaced by a faster time but
that all such times should be retained.
RSServer/RSClient Version 18.104.22.168 Level 2014.01.08
- Andrés Alańón Vázquez reported that
SMS messages with the new Twilio facility did not work in
Spain since the numbers from countries outside the US and
Canada must start with + and RunScore was removing the +
along with the other non-digit characters. Fixed.
RSServer/RSClient Version 22.214.171.124 Level 2014.01.05
- Steve Stone reported that one of his
Announce listing files was not working correctly with the
latest change to the Announce feature. Also, the printing
did not work correctly. Fixed.
- With help from Brian Sparacino, RunScore
supports SMS (cell phone texting) provider: Twilio. They offer
inexpensive texting in the U.S. and a number of other
RSServer/RSClient Version 126.96.36.199 Level 2014.01.02
- John Luaces reported that when he runs
Live Results on RSClient and new finishers come in, the
names are added but not the times. Fixed.