There was a patch involving .Net 4 not recognizing IE 11. So the first thing to do is make sure that the test server is fully patched. This requires a reboot of the server after the patch has been applied.

Inside your if statement where it says "var strbody = ..." should now only be "strbody = ..." since you already declared the variable outside of the if statement. If you look at the modified code I provided in my previous post you will see that I am just assigning a value to the strbody variable inside of the if/else statement.

"strbody" needs to be declared outside of the if statement, so that you can access it outside the scope of the if statement.

@{
string group = Model.ArticleGroupName;
string strbody = string.Empty;

if (group.Contains("Spacial Orientation") || group.Contains("Topography") || group.Contains("Osteology") || group.Contains("Angiology") || group.Contains("Neurology") || group.Contains("Myology") || group.Contains("Radiology") || group.Contains("Misc. Drawings") || group.Contains("Clinical Testing"))
{
strbody = item.ShortBody;
}
else
{

string s = item.ShortBody;
string sLess = s.Remove(0, 12);
int index = sLess.IndexOf("Summary");
strbody = (sLess.Substring(index + 8));
}

}
@strbody

Here is a relatively old article about the architecture of flicker, but it might give you some ideas. http://highscalability.com/flickr-architecture[^]

We are the Borg. Your biological and technological distinctiveness will be added to our own. Resistance is futile.

Your Where clause needs to come after From.

USE IVRCallCenterTest
Go

SELECT *
FROM dbo.OutputPromptItem JOIN
dbo.OutputPrompt ON OutputPromptItem.PromptId = OutputPrompt.PromptID
WHERE SegmentId = 7198
Go

The first thing I see is that your sample path you provided is wrong. You are using the wrong slash in the path, it should be "\\servername\mdain\myfile.xls". The second thing I would check is if the computer you are running the application on has permissions to access the network drive, since that would return false regardless of the file existing.

Something like this should do the trick.

Select ProductName, MySum, field2
From (Select x.ProductName, SUM(x.field1 + y.field2) as MySum, y.field2
From tablexxx as x inner join
tableyyy as y on x.id = y.id) as q
Where MySum - field2 > 0

Response.ContentType = this.FileContentType;
Response.AddHeader("Content-Disposition", "attachment; filename=" + this.FileName);

If the filename has a space in it then either the whole filename should be quoted (and quotes in the string escaped). Or the entire filename should be encoded, which will use %20 to represent a space.

A couple of ways to resolve urls. Virtual Path Utility[^] http://refactoringaspnet.blogspot.com/2009/09/different-approaches-for-resolving-urls.html[^]

You can do the initial credit card validation client side with javascript if you want, but you also need to do the validation server side. Credit Card Validation: 1. Credit Card Number - The credit card number can be validated using the Luhn algorithm[^]. 2. Credit Card Number - You can also validate based on length and prefix if you only accept certain cards[^]. 3. CVV - For most cards it is 3 digits, except American Express which is 4 digits 4. Expiration Date - Date must be greater than or equal to current month and year. Year can be either 2 or 4 digits depending on the Processor API. Month can be either 1 or 2 digits depending on the Processor API. If you are sending the Credit Card information back to the server to process it with the CC Processor, then you need to make sure you are using SSL. Never send Credit Card information over the internet without using a secure connection. Never store credit card information, there are a lot of rules that you need to follow to be PCI Compliant. You agree to be PCI Complaint just by signing up with a Credit Card Processor. The potential fees associated with violations are not worth it, and time required to be fully PCI Complaint. The safest thing to do is only store the TransactionId (or whatever you API calls it), usually that is all you need if later you need to do anything else like void, credit, etc with the Credit Card API. If you want to be able to store the card information so that the user does not have to re-enter the information again, then some Credit Card Processor offer a Customer Manager where they card information is stored on the credit card processors server which would be PCI Complaint. You would then store some sort of Id(s) returned by the Processor and pass those back to the Processor in the future when you want to make another transaction.

MalarGayu wrote:

i am using form authentication using sqlserver as my database and not web.config
 
so that part i am ok as i can compare the values from the database using my own code and getting redirection to a secure page

Your problem probable exists in how you are doing your authorization. It sounds like you are not using the default log-in and membership provider in asp.net by your statement above. Show us the code that you are using to log someone into your site.

The problem is 'OPENQUERY does not accept variables for its arguments.' The following link has a potential work around if you must use OPENQUERY: Passing-variables-into-an-OPENQUERY-argument.

Select Top 1 Code From tblCode Where Code > @Code And CodeName Is Null Order By Code @Code = input from first text box