|
Log in | ||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
I have a requirement to provide a list of all the distinct keys in an
index and the number of occurences of each key. At the moment I open a table, set the appropriate index and in a 'while not table.eof' loop I compile a list of keys and their number. I'm assuming that while this is going on, all the records in their entirety are coming across the network from the server so, on a slow network there's a massive overhead just to get at the index keys. Is there a more effivicient any way of getting at an index and its keys? Dave |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Sequential Access Index | Manfred Abeln | nexusdb.public.support | 4 | 16th December 2009 11:48 AM |
| Sequential Access Index | Manfred Abeln | nexusdb.public.support | 0 | 9th December 2009 08:53 PM |
| Sequential Access Index | Paul Hughes | nexusdb.public.support | 2 | 29th June 2009 10:11 PM |
| Adding a Sequential Access Index | Luke Johnston | nexusdb.public.support | 2 | 12th October 2007 06:38 AM |
| Simple question as regards direct table access vs. SQL | Robert Meek | nexusdb.public.support | 21 | 30th January 2006 11:51 PM |