 |  |  |  |  |  |  |  |
Updated : Simple ASP.Net Login Page
Please support our ASP.NET advertiser: $4.95 a Month - ASP.NET Web Hosting – Click Here!
 |
Original thread - To see why this was Updated
Reason for new thread is to start with a clean slate and I will also be providing a tutorial for SQL and possibly Oracle DB connections to show how easy this code is to implement regardless of the DB you are using.:p
As well, if time permits I may take the time to code this in a few other .Net languages (C#, C++, and J#).
This is sample code for a ASP.Net Login page (using Visual Basic.Net code behind) with OleDB connection to an Access Database using ADO.Net.
Pre-Code Setup::-|
1. Create a New ASP.NET Web Application. I called mine NorthLogin2
2. Rename the default aspx Webform to Login or Index or something more descriptive. I called mine Login2.aspx
3. Assuming you are in Visual Studio.Net right click on this form in the Solution Explorer and Select Set as Start Page.
4. Find your Northwind.mdb file (The classic Northwind Database in Access)
Under Tools, Options, Tables/Queries Tab select Run Permissions as Owner's
5. Create a new table for login requirements. I called mine tblUser
Columns U_id (autonumber), U_Name (text), and U_Password (text with Input Mask of Password)
6. Create Query (i.e. Stored Procedure) to validate login(s). I called mine sp_ValidateUser
In the SQL Designview the code for that query is
This query counts the number of users that it retrieves which matches the where clause. The @UserName and @Password are the values passed in to the query from the Webform.
7. Close database, because you can not access it while it is open.
Let the coding begin::cheesy:
1. Create the API for your Login Webform. You want to have two textboxes for the user to enter their login information. You will also want to have some kind of visual feedback to the user regarding the status of the login; i.e. Is the login successful? Usually that is done by redirecting to the page they are trying to login to. If it is not successful, and whether they provided the information in the two textboxes.
Login2.aspx
As you can see by the above code I require my users to supply a Username and Password, the requirefieldvalidator object does just that.
2.Code for the communication to the database:
a.Add the following line of code to the Web.Config file
- start right after
<?xml version="1.0" encoding="utf-8"?>
<configuration>
These lines of code do several things. 1. Eliminates the need for creation of a connection string (strConn) each time you want to connect to the Database(DB). Who wants to write that out each time. Now you have "pseudo-global" variable for use in your entire application. 2. Makes it secure, so no user can see where the DB is actually located. 3. And most importantly tells the application the location of the said DB.
b.Code the "meat" of the Login in page.
- Mine is in the code behind rather than a script block, but the principles are the same.
- Add the following Imports to your code behind, just above the class declaration.
This will provide the library imports you need for Authentication, accessing an OleDB (i.e. Access), and accessing the web.config file (contains your connection string)
c. Create a Function to connect to the DB return result(s)
- This is the main function of this entire webform.
d. Code the button click event for submitting login to DB
- The code for the onClick event of the Submit button is as follows, but this is very basic and simple. I will be expanding on this further with things like have a maximum number of attempts, and what happens when a user tries to access a page in the application without having logged in; it should redirect the user to the login page/form, otherwise what is the purpose of the login form.
3. Create the page to send the user to once login is successful
- In Visual Studio.Net go to File -> Add New Item -> Webform
- Name it default.aspx
- For ease at this time, just put a text message saying something like "Successful Login".
- It is this page that ASP.Net will automatically look for once login is successful, so if you do not create it you will get an application error.
4. Compile and run your code!
That is the end of this basic outline of a Login Page using ASP.Net. There were some moderate level of difficulty coding, but I believe my comments inline with the code should clarify any questions you may have. If by chance you have some questions, please post them here.
Please DO NOT POST replies to this thread that say things like - "Mine doesn't work!" without providing details of what errors you got, what does happen, etc.
I can't help you if you do not provide details! Let me say that again I can't help you if you do not provide details! And preferably any code alerations you may have done to the above code for your specific
application.
Happy Coding.
Reason for new thread is to start with a clean slate and I will also be providing a tutorial for SQL and possibly Oracle DB connections to show how easy this code is to implement regardless of the DB you are using.:p
As well, if time permits I may take the time to code this in a few other .Net languages (C#, C++, and J#).
This is sample code for a ASP.Net Login page (using Visual Basic.Net code behind) with OleDB connection to an Access Database using ADO.Net.
Pre-Code Setup::-|
1. Create a New ASP.NET Web Application. I called mine NorthLogin2
2. Rename the default aspx Webform to Login or Index or something more descriptive. I called mine Login2.aspx
3. Assuming you are in Visual Studio.Net right click on this form in the Solution Explorer and Select Set as Start Page.
4. Find your Northwind.mdb file (The classic Northwind Database in Access)
Under Tools, Options, Tables/Queries Tab select Run Permissions as Owner's
5. Create a new table for login requirements. I called mine tblUser
Columns U_id (autonumber), U_Name (text), and U_Password (text with Input Mask of Password)
6. Create Query (i.e. Stored Procedure) to validate login(s). I called mine sp_ValidateUser
In the SQL Designview the code for that query is
SELECT COUNT(*) AS Num_of_User
FROM tblUser
WHERE (((tblUser.U_Name)=[@UserName]) AND ((tblUser.U_Password)=[@Password]));This query counts the number of users that it retrieves which matches the where clause. The @UserName and @Password are the values passed in to the query from the Webform.
7. Close database, because you can not access it while it is open.
Let the coding begin::cheesy:
1. Create the API for your Login Webform. You want to have two textboxes for the user to enter their login information. You will also want to have some kind of visual feedback to the user regarding the status of the login; i.e. Is the login successful? Usually that is done by redirecting to the page they are trying to login to. If it is not successful, and whether they provided the information in the two textboxes.
Login2.aspx
<%@ Page Language="vb" AutoEventWireup="false" Codebehind="Login2.aspx.vb" Inherits="NorthLogin2.WebForm1"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Northwind Database Login</title>
<meta content="Microsoft Visual Studio .NET 7.1" name="GENERATOR">
<meta content="Visual Basic .NET 7.1" name="CODE_LANGUAGE">
<meta content="JavaScript" name="vs_defaultClientScript">
<meta content="http://schemas.microsoft.com/intellisense/ie5" name="vs_targetSchema">
<!-- <summary>
||||| Style Sheet |||||
</summary>
--><link title="standard" href="Styles.css" type="text/css" rel="stylesheet">
</head>
<body>
<!-- ||||| Login Form ||||| -->
<form id="frmlogin" method="post" runat="server">
<table id="mainTable">
<tr>
<td>
<table class="t_border" id="loginTable" cellspacing="15" cellpadding="0">
<tr>
<td><b>Login: </b>
</td>
<td><asp:textbox id="txtUserName" runat="server" width="160px"></asp:textbox><asp:requiredfieldvalidator id="rvUserValidator" runat="server" display="None" errormessage="You must supply a Username!"
controltovalidate="txtUserName"></asp:requiredfieldvalidator></td>
</tr>
<tr>
<td><b>Password: </b>
</td>
<td><asp:textbox id="txtPassword" runat="server" width="160px" textmode="Password"></asp:textbox><asp:requiredfieldvalidator id="rvPasswordValidator" runat="server" display="None" errormessage="Empty Passwords not accepted"
controltovalidate="txtPassword"></asp:requiredfieldvalidator></td>
</tr>
<tr>
<td align="center" colspan="2"><asp:button id="cmdSubmit" runat="server" borderstyle="Solid" text="Submit"></asp:button></td>
</tr>
</table>
</td>
</tr>
<tr>
<td>
<table id="messageDisplay">
<tr>
<td><asp:validationsummary id="Validationsummary1" runat="server" width="472px" displaymode="BulletList"></asp:validationsummary></td>
</tr>
</table>
</td>
</tr>
</table>
</form>
<asp:label id="lblMessage" runat="server" width="288px" forecolor="#C00000" font-size="Medium"
font-italic="True" font-bold="True"></asp:label>
<!-- ||||| End of Form ||||| -->
</body>
</html>
As you can see by the above code I require my users to supply a Username and Password, the requirefieldvalidator object does just that.
2.Code for the communication to the database:
a.Add the following line of code to the Web.Config file
- start right after
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<!-- ||||| Application Settings ||||| --> <appSettings> <add key="strConn" value="Provider = Microsoft.Jet.OLEDB.4.0;Data Source=C:\Inetpub\wwwroot\Northwind.mdb;User ID=Admin;Password=;"/> </appSettings> <system.web>
b.Code the "meat" of the Login in page.
- Mine is in the code behind rather than a script block, but the principles are the same.
- Add the following Imports to your code behind, just above the class declaration.
Imports System.Web.Security ' ||||| Required Class for Authentication Imports System.Data ' ||||| DB Accessing Import Imports System.Data.OleDb ' |||||| Access Database Required Import! Imports System.Configuration ' |||||| Required for Web.Config appSettings |||||
c. Create a Function to connect to the DB return result(s)
- This is the main function of this entire webform.
Function DBConnection(ByVal strUserName As String, ByVal strPassword As String) As Boolean [color=#008000]'<sumamry> ' ||||| Declare Required Variables ' ||||| Access appSettings of Web.Config for Connection String (Constant) '</summary> ' ||||| First is the Connection Object for an Access DB Dim MyConn As OleDbConnection = New OleDbConnection(ConfigurationSettings.AppSettings("strConn")) ' ||||| This is the Connections Object for an SQL DB SqlConnection(ConfigurationSettings.AppSettings("strConn")) '<sumamry> ' ||||| Create a OleDb Command Object ' ||||| Pass in Stored procedure ' ||||| Set CommandType to Stored Procedure '</summary> ' ||||| To Access a Stored Procedure in Access - Requires a Command Object Dim MyCmd As New OleDbCommand("sp_ValidateUser", MyConn) ' ||||| To Access a Stored Procedure in SQL Server - Requires a Command Object MyCmd.CommandType = CommandType.StoredProcedure ' ||||| Create Parameter Objects for values passed in Dim objParam1, objParam2 As OleDbParameter '<sumamry> ' ||||| Add the parameters to the parameters collection of the ' ||||| command object, and set their datatypes (OleDbType in this case) '</summary> objParam1 = MyCmd.Parameters.Add("@UserName", OleDbType.Char) objParam2 = MyCmd.Parameters.Add("@Password", OleDbType.Char) '' ||||| Set the direction of the parameters...input, output, etc objParam1.Direction = ParameterDirection.Input objParam2.Direction = ParameterDirection.Input '' ||||| Set the value(s) of the parameters to the passed in values objParam1.Value = strUserName objParam2.Value = strPassword ' ||||| Try, catch block! Try ' ||||| Check if Connection to DB is already open, if not, then open a connection If MyConn.State = ConnectionState.Closed Then ' ||||| DB not already Open...so open it MyConn.Open() End If ' ||||| Create OleDb Data Reader Dim objReader As OleDbDataReader objReader = MyCmd.ExecuteReader(CommandBehavior.CloseConnection) ' ||||| Close the Reader and the Connection Closes with it While objReader.Read() If CStr(objReader.GetValue(0)) <> "1" Then lblMessage.Text = "Invalid Login!" Else objReader.Close() ' ||||| Close the Connections & Reader Return True End If End While Catch ex As Exception lblMessage.Text = "Error Connecting to Database!" End Try End Function
d. Code the button click event for submitting login to DB
- The code for the onClick event of the Submit button is as follows, but this is very basic and simple. I will be expanding on this further with things like have a maximum number of attempts, and what happens when a user tries to access a page in the application without having logged in; it should redirect the user to the login page/form, otherwise what is the purpose of the login form.
Private Sub cmdSubmit_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles cmdSubmit.Click If Page.IsValid Then ' ||||| Meaning the Control Validation was successful! ' ||||| Connect to Database for User Validation ||||| If DBConnection(txtUserName.Text.Trim(), txtPassword.Text.Trim()) Then FormsAuthentication.RedirectFromLoginPage(txtUserName.Text, False) ' ||||| default.aspx Page! Else Else ' ||||| Credentials are Invalid lblMessage.Text = "Invalid Login!" ' ||||| Increment the LoginCount (attempts) 'Session("LoginCount") = CInt(Session("LoginCount")) + 1 ' ||||| Determine the Number of Tries 'If Session("LoginCount").Equals(intMaxLoginAttempts) Then ' Response.Redirect("Denied.aspx") 'End If 'If CInt(Session("Num_of_Tries")) > 2 Then ' ||||| If Exceeds then Deny! ' Response.Redirect("Denied.aspx") 'End If End If End If End Sub
3. Create the page to send the user to once login is successful
- In Visual Studio.Net go to File -> Add New Item -> Webform
- Name it default.aspx
- For ease at this time, just put a text message saying something like "Successful Login".
- It is this page that ASP.Net will automatically look for once login is successful, so if you do not create it you will get an application error.
4. Compile and run your code!
That is the end of this basic outline of a Login Page using ASP.Net. There were some moderate level of difficulty coding, but I believe my comments inline with the code should clarify any questions you may have. If by chance you have some questions, please post them here.
Please DO NOT POST replies to this thread that say things like - "Mine doesn't work!" without providing details of what errors you got, what does happen, etc.
I can't help you if you do not provide details! Let me say that again I can't help you if you do not provide details! And preferably any code alerations you may have done to the above code for your specific
application.
Happy Coding.
SQL Variation on the above Simple Login Page in ASP.Net (w/ VB.Net)
** I am using Visual Studio.Net and SQL Server 2000, but the principles are still the same regardless of your IDE tools ***
1. Follow the above steps for creation of the Application and Page
a. Created a WebForm called the ASP.Net Page Login.aspx
b. Coded the WebForm in HTML
2. Modify the Web.Config file and add the connection string to SQL Server(as was above..BUT DIFFERENT!)
- This assumes your SQL Server is located locally on your system, and not remotely.
- Add these lines of code the Web.Config file just after <configuration>.
Web.Config:
- If the server is located remotely, then there is a slight modification to the connection string to be made
Remote Connection:
- Data Source is the IP Address of the Server hosting the SQL Server DB
- 1433 is the standard port for SQL Server
3. Declare the Imports required
- These give you access to the libraries and data access methods you need to connect the Login Page to the data base.
Imports:
4. As was done in the above example for access, create the OnClick Event code for the Submit Button
- I am using the codebind, rather than the script method of coding the Visual Basic Portion of the Application.
- Once this button is pressed, the ASP.Net Page will validate the data provided by the user before it transmits anything to the server.
- If the date meets the validation criteria, then the event will call the DBConnection Function.
- But before we get to the DBConnection Function, here is the code for the OnClick Event
OnClick_Event:
5. Create the table that stores the User Login Credentials
- This can be easily done in Visual Studio.NET or vial query analyzer.
- Use which ever method you want, I will show the code as you would enter it in query analyzer
Table Script:
6. Insert some data into the newly created table.
- This is just for teaching purposes, but you could wrap this code up into a Store Procedure and use it in a Add New User page in your application.
Insert Script:
7. As in the AccessDB example you must create the stored procedure which takes the values pass to it and validates them against the database.
- The values being passed to the store procedure are the User Name and Password.
- The store procedure can be created by two methods with my setup :
a. In Visual Studio
- Create a server connection to your SQL Server in the Server Explorer.
- Once you have this connection select the Northwind Database
- In the Visual Studio.Net IDE select the Database Menu->New Stored Procedure
- Follow the code sample below to create the stored procedure. **DO NOT Forget to Rename the default stored procedure name i.e.StoreProcedure1**
b. In Query Analyzer
- Create the stored procedure as by following the sample code below
Things to note:
The Store Procedure Script:
8. As in the AccessDB Example of this login page you need to create the DBConnection Function
- You will have to modify the code from the AccessDB example to work for SQL server.
- You will declare a new parameter, add it to the parameter colleciton, and have it set to receive the return value from the stored procedure.
- Determine if the return value is greater than 0 (meaning the SQL DB found the user based on the creditenials provided).
DBConnection Function:
9. Create the default.aspx page (as in the above AccessDB example)
- This is the default page the application will go to following a successful login.
Your SIMPLE (kind of) SQL Login Page is COMPLETE! Compile and Run it, and if you followed my steps it will work!
Hope this helps everyone, and happy coding.
Disclaimer:
There is an even simplier version of this login page, down to the bare minimum of code. But I went the route I did for reasons of expanding, and eventually a tutorial on making this login code into a User Control that you can implement in a number of applications. Thus not having to recode this everytime you do a new application requiring a login.
** I am using Visual Studio.Net and SQL Server 2000, but the principles are still the same regardless of your IDE tools ***
1. Follow the above steps for creation of the Application and Page
a. Created a WebForm called the ASP.Net Page Login.aspx
b. Coded the WebForm in HTML
2. Modify the Web.Config file and add the connection string to SQL Server(as was above..BUT DIFFERENT!)
- This assumes your SQL Server is located locally on your system, and not remotely.
- Add these lines of code the Web.Config file just after <configuration>.
Web.Config:
<!-- ||||| Application Settings ||||| --> <appSettings> <add key="strConn" value="Data Source=(local);database=Northwind;User id=Paladine;Password=;"/> </appSettings> <system.web>
- If the server is located remotely, then there is a slight modification to the connection string to be made
Remote Connection:
<appSettings> <add key="strConn" value="Network Library=DBMSSOCN;Data Source=192.168.0.100,1433;database=Northwind;User id=Paladine;Password=;"/> </appSettings>
- Data Source is the IP Address of the Server hosting the SQL Server DB
- 1433 is the standard port for SQL Server
3. Declare the Imports required
- These give you access to the libraries and data access methods you need to connect the Login Page to the data base.
Imports:
Imports System.Web.Security ' |||||| Required Class for Authentication Imports System.Data ' |||||| DB Accessing Import Imports System.Data.SqlClient ' |||||| SQL Server Import Imports System.Configuration ' |||||| Required for Web.Config appSettings |||||
4. As was done in the above example for access, create the OnClick Event code for the Submit Button
- I am using the codebind, rather than the script method of coding the Visual Basic Portion of the Application.
- Once this button is pressed, the ASP.Net Page will validate the data provided by the user before it transmits anything to the server.
- If the date meets the validation criteria, then the event will call the DBConnection Function.
- But before we get to the DBConnection Function, here is the code for the OnClick Event
OnClick_Event:
Private Sub cmdSubmit_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles cmdSubmit.Click If Page.IsValid Then ' ||||| Meaning the Control Validation was successful! ' ||||| Connect to Database for User Validation ||||| If DBConnection(txtUserName.Text.Trim(), txtPassword.Text.Trim()) Then FormsAuthentication.RedirectFromLoginPage(txtUserName.Text, False) ' ||||| default.aspx Page! Else ' ||||| Credentials are Invalid lblMessage.Text = "Invalid Login!" End If End If End Sub
5. Create the table that stores the User Login Credentials
- This can be easily done in Visual Studio.NET or vial query analyzer.
- Use which ever method you want, I will show the code as you would enter it in query analyzer
Table Script:
CREATE TABLE NorthWindUsers (UserID INT IDENTITY(1,1) NOT NULL, UserName VARCHAR(50) NOT NULL, Password VARCHAR(50) NOT NULL)
6. Insert some data into the newly created table.
- This is just for teaching purposes, but you could wrap this code up into a Store Procedure and use it in a Add New User page in your application.
Insert Script:
INSERT INTO NorthWindUsers (UserName, Password) VALUES ('Admin', 'Admin')
7. As in the AccessDB example you must create the stored procedure which takes the values pass to it and validates them against the database.
- The values being passed to the store procedure are the User Name and Password.
- The store procedure can be created by two methods with my setup :
a. In Visual Studio
- Create a server connection to your SQL Server in the Server Explorer.
- Once you have this connection select the Northwind Database
- In the Visual Studio.Net IDE select the Database Menu->New Stored Procedure
- Follow the code sample below to create the stored procedure. **DO NOT Forget to Rename the default stored procedure name i.e.StoreProcedure1**
b. In Query Analyzer
- Create the stored procedure as by following the sample code below
Things to note:
/* JUST TO SHOW YOU A DIFFERENCE BETWEEN Visual Studio.Net and Query Analyzer */ CREATE PROCEDURE dbo.sp_ValidateUser /* How it would appear in Visual Studio.Net */ CREATE PROCEDURE sp_ValidateUser /* How it would appear in QUERY ANALYZER */
The Store Procedure Script:
CREATE PROCEDURE sp_ValidateUser /* How it would appear in QUERY ANALYZER */ ( @UserName VARCHAR(50) = NULL, @Password VARCHAR(50) = NULL, @Num_of_User INT = 0 ) AS SET @Num_of_User = (SELECT COUNT(*) AS Num_of_User FROM NorthWindUsers WHERE UserName = @UserName AND Password = @Password) RETURN @Num_of_User
8. As in the AccessDB Example of this login page you need to create the DBConnection Function
- You will have to modify the code from the AccessDB example to work for SQL server.
- You will declare a new parameter, add it to the parameter colleciton, and have it set to receive the return value from the stored procedure.
- Determine if the return value is greater than 0 (meaning the SQL DB found the user based on the creditenials provided).
DBConnection Function:
Function DBConnection(ByVal strUserName As String, ByVal strPassword As String) As Boolean '<sumamry> ' ||||| Declare Required Variables ' ||||| Access appSettings of Web.Config for Connection String (Constant) '</summary> ' ||||| This is the Connections Object for an SQL DB Dim MyConn As SqlConnection = New SqlConnection(ConfigurationSettings.AppSettings("strConn")) '<sumamry> ' ||||| Create a OleDb Command Object ' ||||| Pass in Stored procedure ' ||||| Set CommandType to Stored Procedure '</summary> ' ||||| To Access a Stored Procedure in SQL Server - Requires a Command Object Dim MyCmd As New SqlCommand("sp_ValidateUser", MyConn) MyCmd.CommandType = CommandType.StoredProcedure ' ||||| Create Parameter Objects for values passed in Dim objParam1, objParam2 As SqlParameter ' ||||| Create a parameter to store your Return Value from the Stored Procedure Dim objReturnParam As SqlParameter '<sumamry> ' ||||| Add the parameters to the parameters collection of the ' ||||| command object, and set their datatypes (OleDbType in this case) '</summary> objParam1 = MyCmd.Parameters.Add("@UserName", SqlDbType.VarChar) objParam2 = MyCmd.Parameters.Add("@Password", SqlDbType.VarChar) objReturnParam = MyCmd.Parameters.Add("@Num_of_User", SqlDbType.Int) ' ||||| Set the direction of the parameters...input, output, etc objParam1.Direction = ParameterDirection.Input objParam2.Direction = ParameterDirection.Input objReturnParam.Direction = ParameterDirection.ReturnValue ' Note RETURNVALUE '' ||||| Set the value(s) of the parameters to the respective source controls objParam1.Value = txtUserName.Text objParam2.Value = txtPassword.Text ' ||||| Try, catch block! Try ' ||||| Check if Connection to DB is already open, if not, then open a connection If MyConn.State = ConnectionState.Closed Then ' ||||| DB not already Open...so open it MyConn.Open() MyCmd.ExecuteNonQuery() End If ' ||||| Was the return value greater than 0 ??? If objReturnParam.Value < 1 Then lblMessage.Text = "Invalid Login!" Else Return True End If ' ||||| Close the Connection Closes with it MyConn.Close() Catch ex As Exception lblMessage2.Text = "Error Connecting to Database!" End Try End Function
9. Create the default.aspx page (as in the above AccessDB example)
- This is the default page the application will go to following a successful login.
Your SIMPLE (kind of) SQL Login Page is COMPLETE! Compile and Run it, and if you followed my steps it will work!
Hope this helps everyone, and happy coding.
Disclaimer:
There is an even simplier version of this login page, down to the bare minimum of code. But I went the route I did for reasons of expanding, and eventually a tutorial on making this login code into a User Control that you can implement in a number of applications. Thus not having to recode this everytime you do a new application requiring a login.
Last edited by Paladine; Dec 24th, 2005 at 3:09 pm.
Thanks a bunch Paladine. Almost there.
I ran the login page in debug mode and found this:
After MyCmd.ExecuteNonQuery(), it took me to the Catch ex As Exception
I double checked the strConn & Stored Procedure and they both work. Did it work on your DB?
-kendel
I ran the login page in debug mode and found this:
After MyCmd.ExecuteNonQuery(), it took me to the Catch ex As Exception
I double checked the strConn & Stored Procedure and they both work. Did it work on your DB?
-kendel
It's my bad. I didn't know that the params in the SP must match the params in .net page
Your example works perfect. Thanks again.
Your example works perfect. Thanks again.
•
•
•
•
Originally Posted by Kendel
Thanks a bunch Paladine. Almost there.
I ran the login page in debug mode and found this:
After MyCmd.ExecuteNonQuery(), it took me to the Catch ex As Exception
I double checked the strConn & Stored Procedure and they both work. Did it work on your DB?
-kendel
hi Paladine,
i just tried ur code with this change in the webconfig:
<appSettings>
<add key="strConn" value="Provider = SQLOLEDB; Data Source=(local); Initial Catalog=users; Integrated Security=SSPI;"/>
</appSettings>
I get this error:
An analytical error message: Composition section appSettings cannot be
recognized.
Source error:
Line 12:<compilation defaultLanguage="vb" debug="true" />
Line 13:
Line 14:<appSettings>
Line 15:<add key="strConn" value="Provider = SQLOLEDB;Data Source=(local); Initial Catalog=users; Integrated Security=SSPI;"/>
Line 16:</appSettings>
I have a database called users and have a table called tbl_users in users database.
Im stuck using a Jap version of SQL server and visual studio.net, i havent used sql server b4, and dont know how if i saved the query correctly. could you give more details, sorri 2 b such a bother.
Cheers for any help!
i just tried ur code with this change in the webconfig:
<appSettings>
<add key="strConn" value="Provider = SQLOLEDB; Data Source=(local); Initial Catalog=users; Integrated Security=SSPI;"/>
</appSettings>
I get this error:
An analytical error message: Composition section appSettings cannot be
recognized.
Source error:
Line 12:<compilation defaultLanguage="vb" debug="true" />
Line 13:
Line 14:<appSettings>
Line 15:<add key="strConn" value="Provider = SQLOLEDB;Data Source=(local); Initial Catalog=users; Integrated Security=SSPI;"/>
Line 16:</appSettings>
I have a database called users and have a table called tbl_users in users database.
Im stuck using a Jap version of SQL server and visual studio.net, i havent used sql server b4, and dont know how if i saved the query correctly. could you give more details, sorri 2 b such a bother.
Cheers for any help!
hi hi!
i didnt see the 2nd posting u did and i changed my web.config to:
<appSettings>
<add key="strConn" value="Data Source=(local); database=users; user id=sa; password=chaos;"/>
</appSettings>
And i get this error:
An analytical error message: Type 'Final2.Global' was not able to be read.
Source error:
Line 1:<%@ Application Codebehind="Global.asax.vb" Inherits="Final2.Global" %>
im like huh? wats global.asax file do?
i didnt see the 2nd posting u did and i changed my web.config to:
<appSettings>
<add key="strConn" value="Data Source=(local); database=users; user id=sa; password=chaos;"/>
</appSettings>
And i get this error:
An analytical error message: Type 'Final2.Global' was not able to be read.
Source error:
Line 1:<%@ Application Codebehind="Global.asax.vb" Inherits="Final2.Global" %>
im like huh? wats global.asax file do?
Hi Paladine,
i just wanted to know, how can i insert more fields into the exisiting table on sql server?
i just wanted to know, how can i insert more fields into the exisiting table on sql server?
In short. With difficulty. It depends, is there data (more than a few lines that ) in the table? When you modifiy an existing table with data in it, there can be issues with data integrity, as well as how is the new field going to affect the existing rows.
In the case of a few lines data, you can extract that data with Enterprise manager, and then Drop the table, recreate it with the new fields, and then modify the insert statements you exported with Enterprise manager to include data for the new fields...and voila. But it is a little more intensive than I made it sound. Unless you have the original insert statments that first populated the table. Like my example above.
In the case of a few lines data, you can extract that data with Enterprise manager, and then Drop the table, recreate it with the new fields, and then modify the insert statements you exported with Enterprise manager to include data for the new fields...and voila. But it is a little more intensive than I made it sound. Unless you have the original insert statments that first populated the table. Like my example above.
|
Similar Threads
Other Threads in the ASP.NET Forum
- Previous Thread: Login view
- Next Thread: Problem iterating through code to show sales tax
| Thread Tools | Search this Thread |
You need to join our community in order to build your list of favorite forums. You can visit the forum index for a listing of all forums.
Related Forum Features
Latest ASP.NET Posts
- Today's Posts
- Unanswered Threads
.net 2.0 3.5 activexcontrol advice ajax alltypeofvideos asp asp.net bc30451 beginner bottomasp.net browser businesslogiclayer c# c#gridviewcolumn cac checkbox class commonfunctions compatible confirmationcodegeneration content contenttype countryselector courier dataaccesslayer database datagrid datagridview datagridviewcheckbox datalist deployment development dgv dropdownlist dropdownmenu dynamic edit embeddingactivexcontrol fileuploader findcontrol flash flv formatdecimal forms formview gridview gudi homeedition iframe iis javascript jquery listbox menu microsoft mouse mssql multistepregistration nameisnotdeclared news objects panelmasterpagebuttoncontrols problem relationaldatabases reportemail rotatepage schoolproject security serializesmo.table sessionvariables silverlight smartcard software sql sql-server sqlserver2005 ssl textbox tracking treeview unauthorized validatedate validation vb.net video videos virtualdirectory vista visual-studio visualstudio web webapplications webarchitecture webdevelopemnt webdevelopment webprogramming webservice youareanotmemberofthedebuggerusers