I always face this problem, Gui Check points fail whn i rerun the scripts which were run successfully on other machines. Take note that all the files are intact and the objects are also recognized properly.
To over come this, we started verifing Gui objects directly by writing appropriate codes instead of Check points.
Is it the way check points behave to all of you. Now we dont recommend these checkpoints in our projects and use user-defined functions to negate the issue.
GUI checkpoints are a sales pitch from mercury. No need to understand any programming - just click on the object you want to verify. Unfortunately, as you've discovered, the checkpoints are problematic - the expected results files need constant updating (especially bitmap checkpoints). Other problems include different locations of results depending on the call chain, and backwards compatiblility issues with older versions of WinRunner. I think you're on the right track - forget the checkpoints and write your own verification functions.
Now to just figure out how one can get the 'Table_Contents' value without using a GUI checkpoint and without generating a lot of errors...
While an HTML table could have, say, a max of seven columns, not every row will have 7 columns, and I haven't figured out a way to get the number of columns in a given row other than checking the return value of getting the cell data, which unfortunately also reports the error to the test results....
Put a a status var on your get function. when the status goes not E_OK, then you have run out of rows and or columns. Keep a counter in the wrapped looping mechanism to give you an actual count of either.