EzWinScore^® Support

PLEASE NOTE: Effective August 10th, the USPSA Match Results and Classification Upload system will NOT accept any data from any version of EzWinScore prior to 4.03. This is necessary to lay the framework for support of some new website functionality that USPSA has planned.

EzWinScore Home Bug Alerts FAQ What's New Program Updates Palm Classification Files

Current EzWinScore Issues

Date Description

06/21/2008
ISSUE
If a competitor is registered in a match twice (ostensibly to shoot a second division), it is possible that the re-entry will not be flagged AS a re-entry.

AFFECTED VERSIONS:
All current 3.x versions and 2.x legacy versions as well

RESOLUTION
This really is not a bug in EzWinScore. Rather, the only way this can happen is if the stats officers doesn't make use of the documented re-entry features already built into EzWinScore and instead tries to register the competitor manually. Example scenario:

Register "Joe Shooter" normally with his USPSA number for match score;

Register "Joe Shooter (2nd Gun)" without a USPSA number in a different division or even the same division;

Go back in and change "Joe Shooter (2nd Gun)"'s USPSA number to what it should be.

That is not how re-entries in EzWinScore were intended to be processed, and the only reason for doing this is a mistaken belief that match results can't show re-entries. They can. For the correct procedure on how to handle re-entries for either classifier reshoots or Level 1 match re-entries, please see the article on re-entries in the "Frequently Asked Questions" page.

The only required program fix here to be added in a future release is to prevent the registration of two competitors with the same USPSA number (the example shown above counts as two different people with the same USPSA number), or prevent changing an existing competitor's USPSA number to match that of someone already registered.

06/26/2007
ISSUE

(Note: In the illustration above, that REALLY WAS the stage name!)

If a competitor does not get a shot off on a stage because of a major malfunction after the beep, the RO is expected to score the number of misses and number of "failure to engage" penalties on the scoresheet, even though there is no time to record. When the scoresheets arrives in Stats, if you key in the misses and penalties, leave the time blank as an "implied zero" (you cannot physically key zero as a time in EzWinScore) and leave the "Did not Fire" pulldown set to "no", the program will actually accept the score. The competitor's "result" will then, however, erroneously appear at the top of the stage results, albeit without a time or hitfactor, instead of at the bottom with the other "zero" results.

AFFECTED VERSIONS
3.00, 3.01, 3.02, 3.03, 3.04, 3.05, 3.06

RESOLUTION
This is a bug, and it will probably be addressed in the future to prevent people stumbling into it. However, the correct thing to do with any score like this in any version of EzWinScore is to utilize the "Did not Fire" pulldown in the Score Entry form. That's what it is for, and should not be confused with the old and obsolute "Did not Finish".

In the example above, the competitor literally "did not fire" a round on the stage, and this is the intent of this particular control. With "Did not Fire" set to "Yes" as illustrated here, it is understood that the time was zero, so you do not have to key it in yourself; the computer did it for you. (There is nothing in the rulebook that requires you to actually press a "0" or any other numeric key on a computer keyboard to enter a competitor's time!) The entry will then appear at the bottom of the stage listing with a zero time as it should, and also marked "DNF" for "did not FIRE". If you wish, you can enter the competitor's misses and penalties, just to be able to say you did, in fact, completely enter the score in compliance with the rulebook, but the end result will be the same.

05/07/2007
ISSUE
It is possible that a competitor's registration record within a match will contain fields that have null values (that is, no value at all) in them. In the case of the Age field (Jr, Sr, SSR), this can cause a problem when you upload the match webfile.txt file to uspsa.org's major match or local match upload areas. In such an occurance, a competitor with a null age field will not show up in the Pistol Final overall results, but will appear in the various stage results. Changing the age from blank to Jr/Sr/SSr and then changing it back to blank does not work as a resolution for this problem. Please note this is not a pervasive issue; the vast majority of competitors not having a specified Age selected in their match record can have match results uploaded to uspsa.org normally. And also please note the issue affects match results as uploaded to uspsa.org ONLY; your own printed match results listings posted at the range are not affected and are correct. This problem was observed at the 2007 USPSA Area 6 Championship.

AFFECTED VERSIONS
3.00, 3.01

RESOLUTION
Fixed by downloading and applying the EzWinScore current maintenance level, available here.

05/07/2007
ISSUE
When you reset the Power Factor pulldown in the Competitor Registration form for a shooter from "Major" to minor and press the Save cmdbutton, and then later go back to look at this competitor again, his Power Factor pulldown once again says "Major". THIS ANOMOLY HAPPENS WITHIN THIS FORM ONLY; the competitor's power factor is in fact being set internally to "minor"; printed listings will show the competitor as having a "minor" power factor, and (most importantly) the competitor's scores are in fact being correctly calculated with "minor" power factors. This is therefore a cosmetic issue in the Competitor Registration form ONLY. This problem was observed at the 2007 USPSA Area 6 Championship.

AFFECTED VERSIONS
3.00, 3.01

RESOLUTION
Fixed by downloading and applying the EzWinScore current maintenance level, available here. A downside to be aware of, however, is that the previously resolved inconvenience on the Competitor Registration form of a "minor" power factor staying "minor" when you change the division from "Production" to something else will be unfortunately re-introduced. We will work on a proper resolution to both situations in the near future.

04/21/2007
ISSUE
The IPSC system works well when competitors have USPSA member numbers. However, it is legal for a non-USPSA member who is a member of another region to shoot an IPSC match in the US. This leaves us with no way to programmatically determine their alias.

AFFECTED VERSIONS
3.00, 3.01, 3.02, 3.03, 3.04, 3.05, 3.06

RESOLUTION
Actually, this is just a workaround. Such competitors should be registered with no member or a PEN number, and "/ALIAS" added to their surname. For example (as illustrated here):

First Name: Joe
Last Name: Shooter/SURESHOT

Would associate the alias SURESHOT with John Doe at the match in which he was thusly registered.

Please note this is NOT an acceptable way to provide the alias for USPSA members in a pure IPSC match. If the competitor has a USPSA number, do not add the "/ALIAS".

We also ask (and this is important) that if you do this in a pure IPSC match, and later register the same competitor into a subsequent USPSA from your masternames table, please take the /ALIAS back off of the shooter's last name. Otherwise this will cause us problems in processing your USPSA match's activity credit upload.

We will work on a proper resolution for this situation to be released in a future point-release of EZWS.

Return to USPSA home page.

Current EzWinScore Issues
Date	Description
06/21/2008	ISSUE If a competitor is registered in a match twice (ostensibly to shoot a second division), it is possible that the re-entry will not be flagged AS a re-entry. AFFECTED VERSIONS: All current 3.x versions and 2.x legacy versions as well RESOLUTION This really is not a bug in EzWinScore. Rather, the only way this can happen is if the stats officers doesn't make use of the documented re-entry features already built into EzWinScore and instead tries to register the competitor manually. Example scenario: Register "Joe Shooter" normally with his USPSA number for match score; Register "Joe Shooter (2nd Gun)" without a USPSA number in a different division or even the same division; Go back in and change "Joe Shooter (2nd Gun)"'s USPSA number to what it should be. That is not how re-entries in EzWinScore were intended to be processed, and the only reason for doing this is a mistaken belief that match results can't show re-entries. They can. For the correct procedure on how to handle re-entries for either classifier reshoots or Level 1 match re-entries, please see the article on re-entries in the "Frequently Asked Questions" page. The only required program fix here to be added in a future release is to prevent the registration of two competitors with the same USPSA number (the example shown above counts as two different people with the same USPSA number), or prevent changing an existing competitor's USPSA number to match that of someone already registered.
06/26/2007	ISSUE (Note: In the illustration above, that REALLY WAS the stage name!) If a competitor does not get a shot off on a stage because of a major malfunction after the beep, the RO is expected to score the number of misses and number of "failure to engage" penalties on the scoresheet, even though there is no time to record. When the scoresheets arrives in Stats, if you key in the misses and penalties, leave the time blank as an "implied zero" (you cannot physically key zero as a time in EzWinScore) and leave the "Did not Fire" pulldown set to "no", the program will actually accept the score. The competitor's "result" will then, however, erroneously appear at the top of the stage results, albeit without a time or hitfactor, instead of at the bottom with the other "zero" results. AFFECTED VERSIONS 3.00, 3.01, 3.02, 3.03, 3.04, 3.05, 3.06 RESOLUTION This is a bug, and it will probably be addressed in the future to prevent people stumbling into it. However, the correct thing to do with any score like this in any version of EzWinScore is to utilize the "Did not Fire" pulldown in the Score Entry form. That's what it is for, and should not be confused with the old and obsolute "Did not Finish". In the example above, the competitor literally "did not fire" a round on the stage, and this is the intent of this particular control. With "Did not Fire" set to "Yes" as illustrated here, it is *understood* that the time was zero, so you do not have to key it in yourself; the computer did it for you. (There is nothing in the rulebook that requires you to actually press a "0" or any other numeric key on a computer keyboard to enter a competitor's time!) The entry will then appear at the bottom of the stage listing with a zero time as it should, and also marked "DNF" for "did not FIRE". If you wish, you can enter the competitor's misses and penalties, just to be able to say you did, in fact, completely enter the score in compliance with the rulebook, but the end result will be the same.
05/07/2007	ISSUE It is possible that a competitor's registration record within a match will contain fields that have null values (that is, no value at all) in them. In the case of the Age field (Jr, Sr, SSR), this can cause a problem when you upload the match webfile.txt file to uspsa.org's major match or local match upload areas. In such an occurance, a competitor with a null age field will not show up in the Pistol Final overall results, but will appear in the various stage results. Changing the age from blank to Jr/Sr/SSr and then changing it back to blank does not work as a resolution for this problem. Please note this is not a pervasive issue; the vast majority of competitors not having a specified Age selected in their match record can have match results uploaded to uspsa.org normally. And also please note the issue affects match results as uploaded to uspsa.org ONLY; your own printed match results listings posted at the range are not affected and are correct. This problem was observed at the 2007 USPSA Area 6 Championship. AFFECTED VERSIONS 3.00, 3.01 RESOLUTION Fixed by downloading and applying the EzWinScore current maintenance level, available here.
05/07/2007	ISSUE When you reset the Power Factor pulldown in the Competitor Registration form for a shooter from "Major" to minor and press the Save cmdbutton, and then later go back to look at this competitor again, his Power Factor pulldown once again says "Major". THIS ANOMOLY HAPPENS WITHIN THIS FORM ONLY; the competitor's power factor is in fact being set internally to "minor"; printed listings will show the competitor as having a "minor" power factor, and (most importantly) the competitor's scores are in fact being correctly calculated with "minor" power factors. This is therefore a cosmetic issue in the Competitor Registration form ONLY. This problem was observed at the 2007 USPSA Area 6 Championship. AFFECTED VERSIONS 3.00, 3.01 RESOLUTION Fixed by downloading and applying the EzWinScore current maintenance level, available here. A downside to be aware of, however, is that the previously resolved inconvenience on the Competitor Registration form of a "minor" power factor staying "minor" when you change the division from "Production" to something else will be unfortunately re-introduced. We will work on a proper resolution to both situations in the near future.
04/21/2007	ISSUE The IPSC system works well when competitors have USPSA member numbers. However, it is legal for a non-USPSA member who is a member of another region to shoot an IPSC match in the US. This leaves us with no way to programmatically determine their alias. AFFECTED VERSIONS 3.00, 3.01, 3.02, 3.03, 3.04, 3.05, 3.06 RESOLUTION Actually, this is just a workaround. Such competitors should be registered with no member or a PEN number, and "/ALIAS" added to their surname. For example (as illustrated here): First Name: Joe Last Name: Shooter/SURESHOT Would associate the alias SURESHOT with John Doe at the match in which he was thusly registered. Please note this is NOT an acceptable way to provide the alias for USPSA members in a pure IPSC match. If the competitor has a USPSA number, do not add the "/ALIAS". We also ask (and this is important) that if you do this in a pure IPSC match, and later register the same competitor into a subsequent USPSA from your masternames table, please take the /ALIAS back off of the shooter's last name. Otherwise this will cause us problems in processing your USPSA match's activity credit upload. We will work on a proper resolution for this situation to be released in a future point-release of EZWS.

EzWinScore® Support

EzWinScore^® Support