UI performance and large data set in Table Object

Mark Smith mark at maseurope.net
Thu Feb 21 14:37:48 EST 2008

Mark, you might store the data from the database in a custom property  
of the table field, and only show as much data as will fit in the  
field at it's current size.

You'd have to write your own scrolling routines to update the  
display, but it can be done.



On 21 Feb 2008, at 19:04, mfstuart wrote:

> Hi All,
> I have a question about large data sets (thousands of lines) in a  
> table
> object and the slowing down of the UI performance, especially on  
> resizing
> the stack.
> My application interfaces to an MS SQL 2000 database via ODBC. No  
> problem
> there.
> The SQL table I have has over half a million records in it, and  
> this grows
> all the time.
> Potentially, the user could return all records, which would take a  
> while to
> load them all.
> But I've created the interface to allow the user to return a  
> smaller record
> set. This can be alot of records - 10, 30, 40, 50000 thousand or  
> more, or
> just a few hundred. It depends on how the user searches the database.
> Now when large record sets are returned from a search, the UI (user
> interface) slows down, especially when resizing the stack to see more
> records in the table object. When resizing with no records, the UI is
> performs normally with fast resizing.
> Q: has any one seen this before? And if so, how do you handle the  
> drop in UI
> performance?
> Thanx,
> Mark Stuart
> -- 
> View this message in context: http://www.nabble.com/UI-performance- 
> and-large-data-set-in-Table-Object-tp15618647p15618647.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution

More information about the Use-livecode mailing list