Hi Derek, > I'd say most experts would never put 100k records in a grid, ever. GUI > controls aren't designed for this amount of data typically, and it's > fairly un-usable to end users.
Maybe I wasn't so clear. I didn't want to display 100K records in a grid. I have a small cursor with 50 records locally with Accessory Ids and from the other side I have a large 100K records Accessories table with desrcriptions, prices etc... All I want is to display a 50-records grid with the appropriate information. Vassilis ----- Original Message ----- From: "Derek Kalweit" <[EMAIL PROTECTED]> To: <profox@leafe.com> Sent: Thursday, March 01, 2007 10:58 PM Subject: Re: How to join a local and a remote cursor? >> >A little more info on >> > how you're joining and the end need for the cursor might be helpful >> > for us to give you more suitable suggestions... > >> The resulting cursor will be used as recordsource in a grid. Until now I >> used to download all the records from the big table locally and then I >> was >> doing an inner join, but I would like to ask what the experts do in a >> common >> scenario like this. > > I'd say most experts would never put 100k records in a grid, ever. GUI > controls aren't designed for this amount of data typically, and it's > fairly un-usable to end users. > > Personally, if I have data needs this large, I create a 'browser' > form. It has a top section with a text box and a drop-down to control > what field I'm searching on, and then maybe some other drop downs for > additional fields. When the user changes these fields, it executes a > 'filter' method which retrieves records matching the criteria they've > selected and fills the grid. If it's a large table, I always put a > server-side limitation(TOP/LIMIT) to prevent too much data from coming > back-- I usually perform a simple count as well, and display the count > as (500/34394) or something like that. > > This creates a very usable interface for end users to find what they > need. The default filter is usually a subset of all records(all > biz-logic 'open' records, for example). My grids are basically lists > that allow a user to double click to open a form with the information. > I also have a timer that actually triggers the 'filter' based on about > 100ms of inactivity in the filtering controls, which allows people to > type without constant re-queries slowing them down. Some people may > prefer a button so they can filter/retrieve the records on demand > instead of automatically. > > > -- > Derek > > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
