Forum Discussion

Retsam's avatar
Retsam
New Contributor
14 years ago

VBObject() vs. Window() for same control

So I'm looking at two different grids (I'm pretty sure they're Sheridan data grids) in different parts of an application.  One of them is directly a child of its parent form and is recognized by TestComplete as a VBObject, and has useful fields such as Cols, Rows, etc.  The other is nested several levels deep beneath its parent form, and is only recognized as a basic Window() option, and has no useful fields.  

Again, I could be wrong, but I feel that these really are the same type of object and would be able to access the second like the first if it were only recognized by TestComplete.  (They both have the same WndClass "afx:27800000" if that means anything)

3 Replies

  • sastowe's avatar
    sastowe
    Super Contributor
    14 years ago
    When you are looking in the object browser, rather than the object spy, look at the window object parent. Is that a grid? Sometimes I have witnessed that the object that object spy is pointing to is a pic or some other control that aids in resizing or whatever. If I go one object up, I can get to the grid.



    I have no idea if this is your situation, but it is worth a look.
  • Retsam's avatar
    Retsam
    New Contributor
    14 years ago
    It doesn't appear to be.  The immediate parent is a form containing the graph and a few other things.  Above that is a tab control, and above that is the last VBObject that I have access to.  I've looked pretty extensively at that to try to find methods to access the grid from there, but it doesn't seem to have any.
  • Julia_K's avatar
    Julia_K
    Icon for Alumni rankAlumni
    14 years ago
    Hello Ben,

    We would like to reproduce the problem you describe. Could you please contact our Support Team via this web form and send them your tested application or a sample application that demonstrates the problem?

    Thank you in advance.