Server Error in '/ads' Application.

Conversion from string "2010/09/08 13:50" to type 'Date' is not valid.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidCastException: Conversion from string "2010/09/08 13:50" to type 'Date' is not valid.

Source Error:



The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

   <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
    <system.web>
        <compilation debug="true"/>
    </system.web>
</configuration>

 Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:


[InvalidCastException: Conversion from string "2010/09/08 13:50" to type 'Date' is not valid.]
   Microsoft.VisualBasic.CompilerServices.Conversions.ToDate(String Value) +154
   ASP.ABMBanner.getbanner() +679
   ASP.abm_aspx.page_load() +449
   System.Web.Util.CalliHelper.ArglessFunctionCaller(IntPtr fp, Object o) +8
   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +8668019
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627

Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3614

Manual versus Computer Scoring

Manual scoring uses the method of reducing the top by 1MP for everyone time the board was unplayed - the concept is that matchpoints are shared with the pair/s who do not play the board.

Computer scoring uses the Neuberg Formula which factors the frequencies and assumes that if the boards had been played more times the scores on the traveller would have been reproduced proportionately - so if a board is played 10 times instead of 11 it assumes that a complete top would have been achieved 1 x 11/10 i.e. 1.1 times. It then matchpoints on this basis.

The traditional manual adjustment will tend to flatten scores - i.e. my +1100 scores 13MPs instead of the top of 14. In Neuberg it will 13.something. Although there are some highly complex mathematical arguments about this sort of factoring it is the generally adopted method throughout international bridge. You can see the factoring of frequencies directly on the ECatsBridge pages especially on the higher numbered boards which tend to be played less times and so are factored sometimes by 20 or 30 times.

As far as Scorebridge is concerned, if you look at their webpage you will see that Stephen Bligh advertises Simple and Neuberg scoring. He explains that if a club wishes to use Neuberg as ECats does all they need to do is uncheck the box in the program that says Simple scoring and then it will factor the frequencies as described.

Sims Links

General Info