ASP.NET

const string sql = "INSERT INTO CONTRACTOR (CAGE_CODE_EXIST, PRIME_CONTRACTOR_ADDRESS1, PRIME_CONTRACTOR_ADDRESS2, CONTRACTOR_CITY, CONTRACTOR_STATE, CONTRACTOR_POSTAL_CODE)"
                 + " VALUES (@CAGE_CODE_EXIST, @PRIME_CONTRACTOR_ADDRESS1, @PRIME_CONTRACTOR_ADDRESS2, @CONTRACTOR_CITY, @CONTRACTOR_STATE, @CONTRACTOR_POSTAL_CODE)";

string connectionString = WebConfigurationManager.ConnectionStrings["DefaultConnection"].ConnectionString;

using (var connection = new SqlConnection(connectionString))
using (var command = new SqlCommand(sql, connection))
{
    command.Parameters.AddWithValue("@CAGE_CODE_EXIST", lookup.Checked);
    command.Parameters.AddWithValue("@PRIME_CONTRACTOR_ADDRESS1", addr1.Text);
    command.Parameters.AddWithValue("@PRIME_CONTRACTOR_ADDRESS2", addr2.Text);
    command.Parameters.AddWithValue("@CONTRACTOR_CITY", city.Text);
    command.Parameters.AddWithValue("@CONTRACTOR_STATE", state.Text);
    command.Parameters.AddWithValue("@CONTRACTOR_POSTAL_CODE", postalcode.Text);
    
    connection.Open();
    command.ExecuteNonQuery();
}

Bootzilla33 wrote:

Is there a setting on an web form that prevents this from happening.

protected override async Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
{
    var response = await base.SendAsync(request, cancellationToken);
    await LogAsync(request, response);
    return response;
}