Troy Hunt: Everything you ever wanted to know about building a secure password reset feature[^] "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Incredible when the error message tells you exactly what the problem is. :-\ :thumbsup: There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.

What you are trying to do is not a good practice. Why do you want to change the dropdown list after user selected it. Are you making things harder while there might an easier solution for you actually need ???

You'll have to do some code unless you want to only demo features that don't require any code. There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.

Take a look at this link hope this will help you out: Msg 1969 Level 16 State 1 | SQL Server Portal[^] -- Regards, Daniel Jones

When you are inserting a record, The value for Emp_Sal should not contain a comma(,). That is ('Puja',20,000) should be written as ('Puja',20000)

Thanks for the reply, actually even i wanted to dig deep into this topic.

Plenty of definitions here[^]. This space for rent

There are lots of clear descriptions around, try Stacks and Queues[^].

Not really, no... it's a complicated subject. The first thing you need to get sorted is the difference between a variable, a reference, and an instance - because without that, none of the rest of this will make any sense. An instance is an example of a class. Thinking about cars, an instance is a car you can physically get into and drive - it is distinct from all other cars in that it will have a different registration / licence number, may be a different colour, may have a different owner. Each physical car is a different instance of a generic subject "A Car". A reference is a "pointer" to an instance: "my car" is a reference to a physical vehicle, "your car" is a reference to a different one. "This car" could refer to the same vehicle as "my car" now, and to "your car" in a moment as we physically move from one to another. Clearly, you can have many references to the same instance! A variable is a named "place" that holds a value - this could be a number like 12 or 14, or a reference to an instance. So when we say: Car myCar = new Car("Mercedes", "A160", Color.Red); We declare a variable called myCar which holds a reference to an instance which is created via the new keyword. A variable doesn't have to hold a reference: it can hold a value instead: int i = 666; We create a variable called i which contains the value 666 This is important, because we have different names for each type of variable: we call the first one a reference type and the second a value type and how they behave is different. -- We'll get to stack and heap soon, honest! -- When you copy a variable, it's important to know if it's a reference type or value type, because they seem to behave very differently: int i = 666; int j = i; i = i + 1; Console.WriteLine("{0}:{1}", i, j); You expect to get "667:666" because if you didn't, then doing any kind of math would get very difficult! And you do: i and j are value types, so the value in i is copied into j, and then incremented - that doesn't affect the value in j because it's a copy of the value. If you think about variables as "pockets" it makes sense: you have five pennies in your right trouser pocket, and you copy the value to your left trouser pocket - you now have five coins in each pock

I don't know why, Mycroft, that your comment brought to my mind Milton's great sonnet on his blindness, specifically the final line: "They also serve who only stand and wait." "Least impact" could well describe my total presence on CodeProject :) ... and ... yet ... cheers, Bill «In art as in science there is no delight without the detail ... Let me repeat that unless these are thoroughly understood and remembered, all “general ideas” (so easily acquired, so profitably resold) must necessarily remain but worn passports allowing their bearers short cuts from one area of ignorance to another.» Vladimir Nabokov, commentary on translation of “Eugene Onegin.”

A clustered index means that when you get to the end the end leaf of the index, you are at the physical location of the data you are looking for. This makes reading data very fast. None clustered indexes by contrast point to a physical location of data - this means that when you do reach the end leaf on a non-clustered index the disk head may have to move to get you your data. The one downside of a clustered index is that if you have a lot of inserts to the indexed table a clustered index will be disadvantageous. This is because every insert into the table will probably require a reorganisation of the physical location of some rows in the table that are not connected to the rows that you are inserting. The simple answer is - a clustered index is very useful when you have a lot of reading and not much writing. “That which can be asserted without evidence, can be dismissed without evidence.” ― Christopher Hitchens

Member 11161625 wrote: Is this code is correct??? Syntactic it is correct, but it will do nothing, as you instructed it. That is the default behaviour. If you want the "leave" days to be removed from the database when the employee is removed from the database, then you'd want a cascading delete. (ON DELETE CASCADE, not "NO ACTION"). That way you can prevent getting "orphaned" records. If you still need the leave-data from that person and don't want to wipe the records, I'd recommend "ON DELETE SET NULL", since the key would have become invalid - but then the record isn't deleted, just the key is removed - handy if you need the leave-data for statistics or other stuff. Last, there is also a "SET DEFAULT" option; if a manager is deleted from the database, then you might want to automatically update all affected workers to some default-manager. Member 11161625 wrote: Is it will work??? Depends on the specs. Press F5 and see if it does what you expect. Disclaimer; various database-engines may use different keywords and not support them all. Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)

Wonde nailed it, IMHO referential integrity and constraints are the last line of defense to keep the garbage in. They also help with optimisation of course. Never underestimate the power of human stupidity RAH

This property is used to restrict the postback of page every time unnecessarily. check like below in you code. if(!IsPostback) { //this is your first visit. } else { //this is not your first visit. } Sridhar Thota.

better you grab a book, try this one Beginning C# 2008 From Novice to Professional it's a bit old, but it is so good for reference.

At the risk (to my immortal soul) of appearing to re-write code by my esteemed mentor and colleague, OriginalGriff, I'd like to add that there is almost a "standard practice" in the use of Properties in .NET, for example: public class Employee { public Employee() { } public void SetEmployeeName(int authorizationcode, string fname, string lname) { if(AuthorizeOkay(authorizationcode) { FirstName = fname; FamilyName = lname; } else { NotifyUnauthorizedAccess(authorizationcode); } } private string \_firstName; public string FirstName { private set { \_firstName = value; } get { return \_firstName; } } private string \_familyName; public string FamilyName { private set { \_familyName = value; } get { return \_familyName; } } public string FullName { get { return string.Format("{0}, {1}", FirstName, FamilyName); } } } Notes: 1. the variables declared 'private which begin with an underscore character "_" are called "backing fields." 2. the fact that all the 'get methods in the properties are public allows access by all. 3. the use of private 'set methods insure that the data can be changed only using the publicly exposed 'SetEmployeeName method. 4. the code shows a simulation in pseudo-code of the use of an "authorization code" to illustrate the idea that some vital information may be protected from "unauthorized" access. I'm not saying you "should" do anything like that, just suggesting the possibility. You might be asking why there are separate properties for first-name and family-name; consider you have a million records and you want to search for duplicate employee last names: possibly, easier to do with only one "field" to search in each record. Sure, there are lots more "bells and whistles" you could add here: for example, testing in the 'SetEmployeeName method for null values in either first, or family, name input strings. There are tools, like ReSharper, that will let you click on an auto-property name and will create the private backing field and modified set/get methods for you. «I want to stay as close to the edge as I can without going over. Out on the edge you see all kinds of things you can't see from the center

the DataControlRowType can be the following: DataRow EmptyDataRow Footer Header Pager Separator so if the row is a "DataRow" then it is a row with data