John,
I've never tried creating a table with more rows than will fit on the
screen, so I can't answer your question directly. I suspect that the
Constructor won't allow you to define such a table, so at the very least
you'll have to create it or grow it dynamically. But do you really want to
do that? Unless your database is guaranteed to be relatively small, you
could use up alot of memory if your table has one row for every record.
Creating a table that fits on the screen, and then associating each row with
a given database record index via SetItemInt is fast and easy to do. I
don't know if the examples that come with the SDK show this technique, but
the McKeon & Rhodes book does.
Mark Peters
<[EMAIL PROTECTED]> wrote in message news:5950@palm-dev-forum...
>
>
> I've read the SDK, but I find it a bit confusing. The description for
TblInsertRow says that there is no concept of a table larger than the
screen, but goes on to say that any row not displayed is simply marked
unusable or something like that.
>
> My question is can you actually have more rows in a table than are
actually displayed on the screen? I want to create a row for each record in
my database and just mark applicable rows as usable. Then, when the user
refilters/scrolls I could just change which rows are invalid/unusable rather
go back and load more data into the table.
>
> Can I do this?
>
> TIA,
>
> John.
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
