Hi,

Was this happening when the server wasn't receiving any hits other than your test page ?

I was wondering whether the oDataAdapter.Fill() would still close the connection when passed in this way - but it seems that it does so that's not a problem. If you're running this from a page instance it looks OK. I suppose you could test with a hard-coded connection string rather than obtaining it from oApp.

Try adding a oDataAdapter.Dispose

Maybe try the simple version:

Dim lcSQL As String = theusual
Dim oDataSet As DataSet = new DataSet
Dim oDataAdapter as OledbDataAdapter = new OleDbDataAdapter(lcSQl,oProcess.oApp.aConnection(1))
oDataAdapter.Fill(oDataSet)

but, TBH, I don't see why any the above might solve anything....



>Here are the findings of my result. Creating a new application object at every hit doesn't change anything. So, I simplified as much as I can. I created a transaction that will simply issue the following code:
>
>

>            Dim lcSQL As String = ""
>            Dim oCommand As OleDbCommand = New OleDbCommand
>            Dim oConnection As OleDbConnection = New OleDbConnection(oProcess.oApp.aConnection(1))
>            Dim oDataAdapter As OleDbDataAdapter = New OleDbDataAdapter
>            Dim oDataSet As DataSet = New DataSet
>
>            lcSQL = "SELECT Video.Numero,Video.Active2,Video.DateR,Video.Notes_E," + _
>             "Video.Notes_F,Video.Running,Video.VideoT,Video.NoVideoT," + _
>             "Masters.FirstName,Masters.LastName,Video.NoVideoL,Video.NoMaster,Video.NoMaster2,Video.NoMaster3," + _
>             "Video.NoMember," + _
>             "VideoType.Title_" + oProcess.cLanguageLetter + " AS VideoType," + _
>             "VideoLanguage.Title_" + oProcess.cLanguageLetter + " AS VideoLanguage," + _
>             "Programs.ProgramT,Video.NoProgram," + _
>             "IIF(ISNULL(Member.NoSchool),0,Member.NoSchool) AS NoSchool," + _
>             "School.SchoolT,Video.NoClass," + _
>             "VideoClassification.Title_" + oProcess.cLanguageLetter + " AS Classification," + _
>             "Video.Url,School.Url AS SchoolUrl,VideoSize.VideoSizeT," + _
>             "Video.NoMember2,Member2.FirstName,Member2.LastName " + _
>             "FROM Video " + _
>             "INNER JOIN Masters ON Video.NoMaster=Masters.Numero " + _
>             "INNER JOIN VideoType ON Video.NoVideoT=VideoType.Numero " + _
>             "INNER JOIN VideoLanguage ON Video.NoVideoL=VideoLanguage.Numero " + _
>             "LEFT JOIN Programs ON Video.NoProgram=Programs.Numero " + _
>             "LEFT JOIN Member ON Video.NoMember=Member.Numero " + _
>             "LEFT JOIN School ON Member.NoSchool=School.Numero " + _
>             "INNER JOIN VideoClassification ON Video.NoClass=VideoClassification.Numero " + _
>             "INNER JOIN VideoSize ON Video.NoVideoSiz=VideoSize.Numero " + _
>             "LEFT JOIN Member AS Member2 ON Video.NoMember2=Member2.Numero " + _
>             "WHERE Video.Active2 AND Video.Numero=21 ORDER BY Video.VideoT"
>
>            oCommand.Connection = oConnection
>            oCommand.CommandText = lcSQL
>            oDataAdapter.SelectCommand = oCommand
>            oDataAdapter.Fill(oDataSet)
>

>
>My local test application fires four simultaneous calls at every .25 second. It only takes a few seconds before I start getting all kinds of errors. The server processes this transaction about 400 times in a minute. So, I may end up with 10 to 15 errors during that timeframe. The errors reported are as described in the other message. It simply doesn't make any sense. Some fields reported in some of them are not even in the SQL, and worst, not even in the tables that are part of the SQL.
>
>If someone can find something wrong in this code, that would be greatly welcome. I just don't know how I can simplify it more.