Have a read of my posts - I am saying that yes this can be done, however there are too many risks involved for me to consider it a suitable pattern for administration on a database. “That which can be asserted without evidence, can be dismissed without evidence.” ― Christopher Hitchens

vkEE wrote: any ideas? Yes, this seems more appropriate to the ASP.NET forum. Veni, vidi, abiit domum

Null value is returned.

As Mycroft suggests, create the most granular index first. Indexes tend to be more useful when the distribution of data in the indexed column(s) is high. And create one index at a time and rerun the query to see how much performance improvement you've gained, if any. This way, if you find that the query has actually slowed down (which may happen sometimes), you can always disable or drop the index and proceed with the next one.

Hi All, I solved this issue by addressing these two items:\ 1. Regarding the first error, need to remove the following tags in the csproj file 0 blah\blah\blah 4.0 2. Regarding the IIS error, I had to do this: True change to False I have another URL in place, and dont really use the localhost, my website has a defined another url in IIS, like http://mydev.ee.com. But i am still using IIS, how does this still work? many thanks,

vkEE wrote: Am i missing something? Yes, this is the C# forum, you want the ASP.NET one. Veni, vidi, abiit domum

Hi, Maybe that table was dropped or renamed?

vkEE wrote: our seniors want this matter researched since it is a new bug in their test environment. They don't want this bug to migrate to production environment. Unless you are in full control of your environment and able to debug every device-driver, some bugs will remain unsolved. vkEE wrote: It has crashed 3 times the past few months Do you know at what time? Anything in the event-log at that specific time? Does it run under .NET 4? If yes, you could consider making a minidump. vkEE wrote: and it is defined with single hash, #. I was hinting at researching the three. Whether it's the correct one will depend on the context of it's use in the stored procedure. You will have to verify the things mentioned, and again, you'd get a more usefull answer if you provide the code for the stored procedure. MSDN[^] states: There are two types of temporary tables: local and global. They differ from each other in their names, their visibility, and their availability. Local temporary tables have a single number sign (#) as the first character of their names; they are visible only to the current connection for the user, and they are deleted when the user disconnects from the instance of SQL Server. Global temporary tables have two number signs (##) as the first characters of their names; they are visible to any user after they are created, and they are deleted when all users referencing the table disconnect from the instance of SQL Server. ..and it becomes more confusing[^] if you are EXECUTEing dynamic SQL. Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]

vkEE wrote: var x = (from dq in db.Questions where dq.Enabled.Equals(true) && (dq.ExpirationDate == null) ? DateTime.Now.AddYears(10) : dq.ExpirationDate >= DateTime.Now In a word: yes here's how I'd write it using the "Null coalescing operator": (see The C# ?? null coalescing operator (and using it with LINQ)[^] var x = (from dq in db.Questions where dq.Enabled && (dq.ExpirationData ?? DateTime.Now.AddYears(10)) >= DateTime.Now) If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein

Here's an example from BOL (2k8): CREATE TABLE dbo.doc_exy (column_a INT ) ; GO INSERT INTO dbo.doc_exy (column_a) VALUES (10) ; GO Straightforwardly: SELECT * FROM dbo.doc_exy Gets: 10 Now, doing the operation appears to suggest that no default value is ever needed: ALTER TABLE dbo.doc_exy ALTER COLUMN column_a DECIMAL (5, 2); GO SELECT * FROM dbo.doc_exy Shows what I mean: 10.00 DROP TABLE dbo.doc_exy ; GO

Either SQL isn't running (or isn't accepting connections) on your QA server, or you've got the wrong connection string somewhere in your config file or code. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

try it in jquery ready function. $(document).ready(function() { var hiddenVal=$("#YourId").val(); }); if you use master page in aspx, then you can find the element by name also. $("input[name='elementName']")

vkEE wrote: How did you know we have to create a new variable to do this? The fact we are treating it as new string? Funny question actually. My personal evolution in this, is that I started out using new variables and copies for everything. As we tend to divide a problem in smaller problems, transforming data (eg sorting a string) or other problems result in the creation of new variables to keep track of things (solutions to each smaller problem). The more experience you gain through the years, the more compact I would start to develop, creating less and less variables. V. (MQOTD Rules and previous Solutions )

Whenever you are posting back you can access Request.Form["ElementName"] to get what was the value before the form got posted. I did not understand the purpose of "linq statement that loads this dynamic panel". Can you tell me what is the architecture you are using. Is it Asp .Net Forms or MVC?

See point #1 in How to get an answer to your question[^] above. Try the: ASP.NET forum[^]

Try dispQuestions.Count**()** instead.