The showcursor class uses the same constant. But if you change the value of the constant, you will need to manually recompile the class to get it to use the new value.

>That constant is used by wwHTML::ShowCursor. I just figured out that for the wwShowCursor class, I needed to set its .nForceToPREList property, which seems to have a default of 4000 cells, same as the value of MAX_TABLE_CELLS in the sample code. I pushed it up to 20000 with no ill effects, and now I get a nice huge table. What the users do with it is up to them, I suppose.
>
>>Bret, the number of cells allowed before formatting goes to broken like this is set in a constant in wconnect.h: MAX_TABLE_CELLS.
>>
>>
>>>I have a more serious problem now. If the cursor has over 500 records + or -, wwShowCursor screws up the formatting. Instead of nice little shaded, bordered boxes, I get plain text separated by pipe characters. Everything else works fine. I implemented the paging display with cookie and all, but that didn't help. wwHTML::ShowCursor has exactly the same problem.
>>>
>>>>Hi Bret,
>>>>I'm doing much the same thing right now. ShowCursor() displays as an HTML table, so you can roll your own with SCAN, filling in the table rows/columns as you wish.
>>>>
>>>>Now if only you could solve my "hidden fields" problem.....
>>>>
>>>>Barbara
>>>>
>>>>>I'm making a demo intranet app which I will show my bosses in order to get them to buy Web Connection. I want to duplicate their existing reports, more or less. I have been playing around with wwShowCursor. Is there anything like that which does grouping? All I can think of is to make a cursor that joins parent and child tables, scan through it, and make alternate parameterized cursors that select "group header" records, display them one at a time with wwShowCursor::ShowRecord() or ::ShowCursor() and select the child records and do another ::ShowCursor(). That won't be so bad. Is that what people do?