Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Major mixup in two ASP.NET transactions
Message
From
01/10/2006 22:09:07
 
 
General information
Forum:
ASP.NET
Category:
Other
Environment versions
Environment:
VB 8.0
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01150471
Message ID:
01158481
Views:
69
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.
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform