So 121 is your row count then yes? You're happy that's the correct number?
I don't know how you address cells in this grid type as I've never used it. Your earlier screen shot showed a "wValue" property, which requires parameter(s) to expose it's value or underlying components. It might be that? (Say - "wValue(1,1)" might return the contents of the cell at position 1,1 - as baxatob posted in his code snippet) I don't know. As I say, different grid types present their data in different ways.
I don't see anything else in your screenshots that looks like it may relate to the current cell. From what I can see on the screenshots, "wValue" and "wColumn" both take parameters, and can be drilled down further. Could be those. Could be another property .... impossible to say without seeing them.
So the problem is that we can't obtain a wRowCount property.
Not sure about Magic xpa application, but there is a limitation for Borland grids: The property can also be unavailable to your scripts if it is not used in the application code. Link , see "Remarks" >>
Possibly that is a peculiarity of compilation and it can be solved together with developers.
As a workaround you can hard-code a row count.
Whereas the behaviour of my Component One Delphi grids is different again.
This is what I'm saying. They are all different. They all behave and are driven differently. What applies to one may not apply to another. So second guessing what a Magic xpa grid will do based on what a Borland or Component One grid does is no more than that ..... a guess.
You want concrete answers, you need to know the base class to associate it with. And even then, that's just the base class. Whether it works and behaves the same is entirely dependent on how much has been modified.
And he has the row count now. I think. Now he's trying to work out how to address a cell. wValue (as per your code snippet) being my first suggested to place to try. But again, we don't know this class, so it's all guesswork.
