>I haven't been able to see any real difference between the form that works and the 3 which do not. They each have one grid and a set of text buttons. No other objects on the form. Each grid is populated from one free table. It's very simple.
>
>The users have to manipulate this data to some degree. They are scheduling deliveries of Roof Tile, so it's being used like a spreadsheet. We used to use a spreadsheet, but that's too cumbersome now. The company is growing. They need to work within the table with no intermediate processes.
>
>Bottom line -- Form with one grid, one button set and one free table. This should be a no-brainer.

I don't know what is wrong with your forms, but I do know that the txtbtns class was not exactly intended to be used in this way. Did you create these forms with the form wizard, or just plop the class onto a blank form and add the grid? The form wizard puts a value in the grid.Tag property, I believe, which is used in some method of txtbtns or maybe searchclass. txtbtns was probably written with the assumption that the grid contains a child cursor and that there is also a parent cursor which is selected by default when the form opens. I don't know whether methods like GetGridRef() and properties like .Gridref and .Gridalias take into account the possibility that the grid cursor is the only cursor. That might not be very helpful, but might at least give an idea of what to look for.

I didn't see a "wiztxtbtns" class library, or whatever, in vfp6. I see "wizstyle" which is the one used by the nasty ol' form wizard since vfp3, and "wizbtns" which is new to me but seems to also contain txtbtns, searchform, and searchclass classes the same as or similar to the ones in wizstyle. I am assuming that you meant one of those.