This is further reinforced by the fact that you are getting an IndexOutOfRangeException in a place where there can't possibly be one - unless there's some cross-threading going on. The most common cause of the big red X is that your application is crossing threads without proper marshalling and something is getting out of synch. Here is a screen snapshot of the error stack:Įverything you are saying here screams "Threading issue" to me. The error indicates "IndexOutOfRangeException" and I cannot understand how this could happen. It causes a big red x on the dgSignOnList datagrid. 'the exception happens on the following line. Private Sub dgSignOnList_InitializeRow(ByVal sender As Object, ByVal e As ) Handles dgSignOnList.InitializeRow 'finally, the datasource change fires the initializerow event when the exception occurs The stack trace indicated an "index out of range" issue, but how could that happen on an initializerow? Could this issue be camouflaging a different issue? Any ideas where I might look?ĭim MyRelationGrptag As New DataRelation("TagdataToGrpTag", ds.Tables("Tagdata").Columns("reqno8"), ds.Tables("grptag").Columns("reqno11"))ĭim fkc3 As ForeignKe圜onstraint = ds.Relations("TagdataToGrptag").ChildKe圜onstraintįkc3.AcceptRejectRule = AcceptRejectRule.CascadeĭgSignOnList.DataSource = ds.Tables("tagdata").DefaultViewĭgSignOnList.DataMember = "TagdataToGrpTag" I understand that the RED X issue has to do with the ONPAINT routine, but I am at a loss as to what might be causing this particular instance of the problem. This started after the system was moved from a local sql server to the Amazon Cloud environment (AWS). Our system is experiencing the BIG RED X on a datagrid (ver 1.2132).
0 Comments
Leave a Reply. |