The connection was not closed. The connection's current state is open?

The problem is you call conn.Close() twice. Retain your Close connection on your finally block.

The problem is you call conn.Close() twice. Retain your Close connection on your finally block. Try If functionmode = "ADD" Then //Supposed this is you columnNAmes //Set parameters SQLStr = "INSERT INTO boatmast (gBoatType,BoatCode,BoatName,BP, BPM,LDA,bpk,Today,updtime,bpk2,Today2,updtime2) VALUES (@gBoatType,@BoatCode,@BoatName,@BP, @BPM,@LDA,@bpk,@Today,@updtime,@bpk2,@Today2,@updtime2)" SQLCmd.Parameters.

AddWithValue("@gBoatType",gBoatType) //DO OTHER STUFF TIL @updtime2 conn.Open() SQLCmd. Connection = conn SQLCmd. CommandText = SQLStr SQLCmd.ExecuteNonQuery() End If Catch ex As OdbcException MsgBox(ex.

ToString) Finally If conn. State = ConnectionState. Open Then conn.Close() End Try Regards.

If SQLCmd.ExecuteNonQuery() fails, it will never close the connection. – Hand-E-Food yesterday Then...Place it on Finally block..Thanks Sir. I just edited my post.

– BizApps yesterday nothing changes – Peterson Agas yesterday maybe there is also duplicate conn.Close() on your other codes aside on what you posted. Can you post your full code? @Peterson Agas – BizApps yesterday done..thank you – Peterson Agas 23 hours ago.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.