Have you tried populating the wValue parameters in the object spy and seeing where that takes you?
I was guessing/speculating that may be the current cell. As I said at the time, it's a guess, we don't know this control, it may well not be. Many grids do use wValue. But others don't My Delphi ones (Component One data driven grids) don't - and theres no point telling you what mine use, they're data driven so use an associated data component making them an entirely different animal. So it may be that you need to use a different property.
Theres the thing.
We don't know these controls. (Rather worryingly, neither do your development people it seems!) It may not be derived from a know class, it maybe completely a standalone third party control. We just don't know and googling didn't find anything that confirmed anything either way.
It may just be blind luck that associating it with one type of known Grid control gets you more access.
But at the end of the day, if TestComplete doesn't support it, you may just have to accept that. Leaving your only option as compiling with debug info and seeing if that gets you any native stuff that isn't otherwise exposed.
Have you had a good poke around in the properties? And by that I mean if it's possible to drill down (ellipses on the right) then you have. Possibly more than one level. If it's possible to give it parameters ("params" on the left) then you have - which may pull back info, it may expose extra layers, it may do both. Many objects, especially complex ones like grids, are more than one layer deep. If you don't have supportive, knowledgeable, on hand to help. Or good explanatory documentation for a control, the best you can do is explore until you find what you need. Like you did with the row count. Cells often/usually require parameters. I suspect you need to dig harder ....
Colin_McCrae I've tried to add grid'classename to every component category independently that exist by default in object mapping setting so I can find the correct one, and it seems that the Microsoft Controls/WinForms/DataGridView is the nerest one that I could find. For every other component type, it gives me more exceptions in type relative properties when I track my object in Object Spy
