sInfo _START_ for server-side and bStateSave = true

mg

When my initial server-side load of the table is, say,
for a table of 500+ rows, and then I page to the 150th row,
and leave the page.

Then I go back to the page, and this time I load the table
for a scenario where it only has 20 rows.

Well, the _START_ value shows as 150,
and thus no records are shown at all.

How can the _START be set back to 0 in these cases?

mg

Perhaps this is not the best method, but it may work in some cases:
try to give the table's css ID a unique value for the particular session
(for instance, if you selected a Company, append the CompanyID to the
table ID). That way, the _START_value should be unique based on the criteria
generating the table.