VBFlexGrid Control (Replacement of the MSFlexGrid control)

[Schmidt]

So, this is not a paged-mode Binding-class.

No, any normal "Rs-Binding-Class" (with support for Updates, Deletes, Inserts) will work *also* in paged mode.

Each programmer will have to independently handle all the events of deleting and changing records...

No - all of these actions will work on the "currently Bound Sub RecordSet" without problems.

...moving through pages, searching, filtering and so on.

And only that requires a few (trivial) extra-lines in the Form-Code
(where also the "Paging-Buttons" with their Click-Events reside anyways).

I guess it is your not (yet) existing experience with Disconnected-Rs (and the UpdateBatch-method they support)?

All the CRUD-actions will accumulate "within" such an Rs - and will be synchronized with the DB,
when you call Rs.UpdateBatch (in the Form).

And it doesn't matter at all in this mode, whether the (currently bound) Rs represents:
- a whole table
- or if it's just a "Where Clause filtered SubSet" (derived from that table)

As for Filtering (on top of the Page-based SQL Limit-Filter-conditions) ...
If the Where-Clause (on a larger table) is restricting the returned Rs.Recordcount so much,
that it sits below your given "Max-Records-Per-Page limit" - then the paging-buttons will simply be disabled -
but the Binding (on that heavily filtered Rs) will work "as always" (supporting Update, Deletes, Inserts) on that smaller Rs.

Olaf