Forum Discussion

Soren's avatar
Soren
Occasional Contributor
9 years ago

Error in wRowCount & wColunmCount

Hi,

Stil something of a noob here, but lately we have experienced that several of our scripts started failing when working with Microsoft DataGridViews.

 

We noticed that wRowCount & wColumnCount were througthing the following errors:

 

Error: Error

An error occurred.

Possible reasons:

  1. The application stopped responding.
  2. The application was compiled incorrectly (see the Open Applications topic in the help system).
  3. An error occurred in TestComplete.

 

Technical information:

351 0x80020003 (Member not found.)

 

& 

 

97 0x80020006 (Unknown name.) dataGridRowsLength

 

How do we resolved thos errors?

 

I have attached a few screenshots of the wRowcount and wColumncount as well as one of the Fullpath name.

 

I will just mention that we have added our Nis.WinForms.Controls.persistentDataGridviewBase to the the Object Mapping.

 

Hope someone can give us a clue or a way to resolve the issue.

 

Kind Regards

 

Soren

4 Replies

Sort By
  • NisHera's avatar
    NisHera
    Valued Contributor
    9 years ago

    have you compiled your application such that test complete can access it internal objects? more info

    did you read this ?

    • Soren's avatar
      Soren
      Occasional Contributor
      9 years ago

      Thank you for the suggestion - yes the application is complied so TestComplete can "sink" its hooks into it and we have checked the installed Extensions support our .Net application.

       

      The scripts we run are inspired by the examples in the support section and we follow the methodes suggested there when we work with datagridviews.

       

      kind regards

       

      Soren

       

       

      • NisHera's avatar
        NisHera
        Valued Contributor
        9 years ago

        I think better to contact TC suppot team

  • avs262's avatar
    avs262
    New Contributor
    6 years ago

    Soren did you ever solve this? I'm experiencing the same issue. I've opened a ticket with support and will post here if a solution is found.