EXE CRACKER
New Member
I've been doing a project in visual studio 2010 for about a week. I'm using vb and a simple sql database. I'm attempting to make a login page that checks whether there is a record in the customer table with the specified email and password. I've come to a point where I'm out of my debugging depth, can anyone see whats causing the error?the Login.aspx.vb file for the Login web form looks like this:\[code\]Imports LoginTableAdaptersPartial Class Login Inherits System.Web.UI.PageDim LoginAdapter As LoginTableAdapterProtected Sub Button1_Click(sender As Object, e As System.EventArgs) Handles Button1.Click Dim email As String Dim pass As String LoginAdapter = New LoginTableAdapter email = TextBox1.Text pass = TextBox2.Text If Me.LoginAdapter.QueryLogin(email, pass) Then Label1.Visible = True End If End SubEnd Class\[/code\]The SQL for QueryLogin() looks like this:\[code\]SELECT custemail, custpasswordFROM customerWHERE (custemail = @Param1) AND (custpassword = @Param2)\[/code\]And this is the error that only happens when entering a correct user/pass combination:\[code\]Server Error in '/DinnerNow' Application.Input string was not in a correct format.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.FormatException: Input string was not in a correct format.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:[FormatException: Input string was not in a correct format.] Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat) +181 Microsoft.VisualBasic.CompilerServices.Conversions.ToBoolean(String Value) +147[InvalidCastException: Conversion from string "[email protected]" to type 'Boolean' is not valid.] Microsoft.VisualBasic.CompilerServices.Conversions.ToBoolean(String Value) +337 Microsoft.VisualBasic.CompilerServices.Conversions.ToBoolean(Object Value) +1304756 Login.Button1_Click(Object sender, EventArgs e) +104 System.Web.UI.WebControls.Button.OnClick(EventArgs e) +9553178 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +103 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +10 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +35 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1724\[/code\]