I have a problem that is driving me NUTS. I have this simple form with some shipping data, that I send to an asp file processshippingdetails.asp, the process scripts are there, and then the form redirects. Simple. In fact, in this application I am using the same code (copied the files and just changed the variables) to process a couple of other forms.

But this one form, its bizaare. Sometimes it creates duplicate entries. Same exact time stamp down to the second. No noticable lag in the processing. I know the button is not being hit twice because ive tested it carefully.

It doesnt happen every time - maybe about 40% of the time, I simply get two exact duplicates. Anyone seen this before? Any guesses? Because at this point I really have NO idea where else to go with this.

It sounds to me that your code is somehow adding an extra, duplicate record to the database about 40% of the time.
Is this correct?

If so, there could be a number of problems. One place to start is to show us the code in procssshippingdetails.asp that does the inserting into the database.

Woody Z http://www.learntoprogramnow.com

Well, this is it. Please forgive the juvenile code...im not actually a programmer, im an office manager who learned to program to help out here and there!


<%
    Dim JobID, Carrier, CarrierID, objC, strC, Comments, shippingaddressID, city, state, strS, objS, cost, PLTSWeight, ShipDate, DelDate

    JobID = Request.Form("JobID")
    If NOT Request.Form("CarrierID") = "" Then
        CarrierID = Request.Form("CarrierID")
    Else
        Carrier = Request.Form("Carrier")

            Set objC = Server.CreateObject("ADODB.Recordset")
            strC = "SELECT * FROM Carrier"
            objC.Open strC, strConnect, adOpenKeyset, adLockOptimistic

            objC.MoveLast
            objC.AddNew
            objC("CarrierName") = Carrier
            objC.Update

            CarrierID = objC("CarrierID")
            objC.Close
    End IF

    Comments = Request.Form("Comments")

    ShippingAddressID = Request.Form("ShippingAddressID")
    If NOT ShippingAddressID = 0 Then
        Set objS = Server.CreateObject("ADODB.Recordset")
        strS = "SELECT * FROM ShippingAddressID =" & ShippingAddressID
        objS.Open strS, strConnect, adOpenKeyset, adLockOptimistic

        City = objS("City")
        State = objS("State")
    Else
        City = Request.Form("City")
        State = Request.Form("State")
    End If

    If NOT Request.Form("Quote") = "" Then
        Cost = Request.Form("Quote")
    Else
        Cost = 0
    End If
    PLTSWeight = Request.Form("Weight")
    ShipDate = Request.Form("pMonth") & "/" & Request.Form("pDay") & "/" & Request.Form("pYear")
    DelDate = Request.Form("dMonth") & "/" & Request.Form("dDay") & "/" & Request.Form("dYear")

    Dim objA, strA

    Set objA = Server.CreateObject("ADODB.Recordset")
    strA = "SELECT * FROM Shipments"
    objA.Open strA, strConnect, adOpenKeyset, adLockOptimistic

    objA.MoveLast
    objA.AddNew

    objA("Date") = Now
    objA("JobID") = JobID
    objA("CarrierID") = CarrierID
    objA("Cost") = Cost
    objA("DatetoShip") = ShipDate
    objA("DatetoArrive") = DelDate
    objA("PLTSWeight") = PLTSWeight
    objA("Comments") = Comments
    objA("City") = City
    objA("State") = State
    objA.Update
    objA.Close

If Request.QueryString("Action") = "another" Then
    Response.Redirect "shippingdetails.asp?action=another&JobID=" & JobID& "&CarrierID="& CarrierID
Else
    Response.Redirect "createshippingentry.asp"
End IF

%>

Well... the only place where it seems to me that another record could be getting created is in the following code if the shippingdetails.asp or createshippingentry.asp redirects have any code that saves a record during the serving of the page:

However, there seems to be some troubling code here.
For example, does this sql statement actually work???:

I can't imagine that is actually works without an error as that is a malformed sql statement.

Also, these bits of code could eventually become a serious performance issue:

You are retrieving ALL carriers or shipments just to insert a single carrier.
A better way to do is:
This will retrieve an empty recordset to which you can add a new record. NOTE: You will not want to use the objC.MoveNext line in this case.

Woody Z http://www.learntoprogramnow.com

The really troublesome line probably wouldnt work....its a function that I hope to use somewhere down the line, the data is not in place to ever have it called yet. But I did fix it. And thanks for the tip on the calling ID=0 thing....I taught myself from books and web queries and tend to make a lot of guesses at what will work!

I know its not the other pages. The ONLY asp on them is to fill in a drop down box. Just very weird. Perhaps with your suggestions it will work more smoothly.

Thanks!

If this is the only code that can insert records into that table, I would suggest that it is possible that the user is using the back-button and clicking the submit button a second time. If this is the actual, working code then there is nothing here that I can see that would cause a duplicate entry to be created in the Shipments table.

Woody Z http://www.learntoprogramnow.com

I'd have to go agree with Woody on this. Just looking at your code, I don't see anywhere in it that would cause a duplicate record. Which table is the dupe appearing in? (or is it both?)

Also, are you absolutely positive that shippingdetails.asp and createshippingentry.asp have no asp code? No redirects or anything? That's about the only thing I can see that would cause an issue here too. Maybe when you see the duplicate record, see which page you were forwarded to. If it's the same page all the time, perhaps there is code in that page that is causing the issue.