Comments by dfarr1 (Top 24 by date)

I changed to the view I posted up earlier, cleaned up a few dateparts, but still am getting the error. Here's the best representation of what it looks like:

string qpart1 = " DATEPART(WEEK, [modifiedCreateDate]) = DATEPART(WEEK, getdate()) ";
string sql6 = "select AVG(WorkHourDiff) AS 'Response Time' from LFM_Archive.dbo.IT_Statistics where" + qpart1;
SqlCommand cmd6 = new SqlCommand(sql6, conn);
conn.Open();
SqlDataReader reader6 = cmd6.ExecuteReader();
while (reader6.Read())
{
int value = 0;
value = (int)reader6["Response Time"];
}
conn.Close();


I've also tried ramming the query string straight into the sqlcommand but that didn't make a difference.

I tried using this as the query string, but the error remains to be "Incorrect syntax near 'DATEPART'" :(

It compiles fine - when you go to production and run the query on an onclick event, I am catching the exception message in a label. The message reads: "Incorrect syntax near 'DATEPART'"

check the question for the attempt of the view

That might work, but we're not worried about the d/t format because when it's inserted or updated into the DB it is always the same format as defined by in the C# backend.

Because the last portion of the query is a variable (to get the output by day, week, month, last 3 months, year, last 5 years) so a stored procedure may not be appropriate. I am thinking that a view might though, and then just do the variable from the C# and leave the bulk of the query there.

It's a sql query called as a report with a variable to modify the range of dates it covers, like where datepart(week, [modifiedcreatedate]) = datepart(week,getdate()). In SMS I'm running it as a query without the variable (as is above). I've tried running with and without the time modifier to no avail.

That was clean as well. I might have found it - Visual Studio keeps it's own tabs on directory contents listing of the bin and obj folders where after looking at it from the VS side, the files that kept causing errors were all flagged with warnings as having potentially missing items. I deleted the folders from the actual directory and not through VS, so it's possible that VS kept trying to reference them because it didn't know I messed with those folders outside the application. It looks to be compiling now but I'll post back to verify whether that was it.

Yes, all the dotnetauth/oauth references have been removed from that list.

Perfect! That's exactly what I needed. Referring to my code, the SearchText2 function in svcfunctions.js was my guinea pig. BELOW the function for "source:" I put in the select function and tested both as displaying the selected value as well as what has become the contents of the textbox. Both worked. This is outstanding :)

For others: yeah, the source vinay.Singh linked as about MVC ASP.NET but it doesn't really matter. You should be putting your functions in a .js page, and the format of the controls you'll map with jquery are identical. The only part in the article that's different is the code that surrounds the functions, which is a bit superfluous as long as you've already got something to work with in your preferred model.

Added that, didn't seem to make a difference. I have a feeling the root of the problem is not in the syntax of the extender or controls but either in initialization by conflict or because the web service is bad.

I had it as <asp:ToolkitScriptManager> and changed it, but it didn't seem to matter. I'm updating the question to include this chunk from the Site.Master

SCRATCH THAT - I got back from lunch, tried it, got that error, then noticed I was doing it on a previous attempt at the code, the newest attempt, with your suggestion, worked perfectly. It posted the test integer into the DB. Issue resolved!! *happy dance*

I took the quotes out and now I get "An SqlParameter with ParameterName '@trackingid' is not contained by this SqlParameterCollection." I am not sure out to pass the ID as a string value to the parameter while passing an int value to the nchar field. From what I can tell, it seems add has been deprecated for clarity reasons while the addwithvalue is newer but has the same function - basically, yeah I could use it, but it wouldn't make a difference as far as I could tell.

Changing from Full to [Full] and adding single quotes into the column title as ('@TrackingID') helped but I was left with the following exception as referenced in my most recent update: "String or binary data would be truncated. The statement has been terminated."

Good point. Here it is: "Incorrect syntax near the keyword 'Full'."

I realized that and then just added it to the Catch. Here's the exception: "Incorrect syntax near the keyword 'Full'."

It always sends a failed message and never actually inserts anything to the DB

I added the .aspx and .cs from the old to the new, added ADConnectionString to web.config, and added tokens to the .cs and the .aspx to prevent cross-site scripting (it forced me to as per the references). You can now get to the page, fill in the info, but when you click 'Submit' it blanks the page and does nothing. Still need help.