Hi Neil.

23-Jan-03 19:07:02, Neil Heller wrote to Jasen Betts


 JB>> Maybe make a clase that behaves like a linked list but is really
 JB>> just a wrapper around a temporary table. like one created by a
 JB>> "selelct-from" SQL query.       ..`` ... ......''''' what's the
 JB>> correct term in this context? is it "view"?

 NH> I know what you're talking about and the idea of a "view" says it
 NH> descriptively.  Currently I'm taking the data from the table
 NH> generated by the SQL query, formatting it and passing it into a
 NH> list box (which is on a separate screen and in a separate class).

 JB>> AFAICT linked lists aren't really needed unless you're planning
 JB>> on inserting into them, or making individual deletions....

 NH> I've found that a linked list works great for passing information
 NH> for which the number of items can't be known before-hand.

once you get the result can't you ask for a count of the records then make an
array?

or you could pass any object that has access to the query result and
methods similar to those of a linked list.

effectively tranalsting the sql result for the listbox....

that way if there's 1000 hits the listbox may not need access count them all

If you leave as much data in database as possible, your code will scale
better because the database load will be lower.

I've seen badly written database applications die horribly when the number
of users climbed, but those guys weren't even using odbc AFAIK. if they
were they could have goone with a big SQL server
whaty they were doing instead was relying on shared DBF files...

 -=> Bye <=-
---