Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.paradox    |    To crash or not to crash, asks Borland    |    9,834 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,856 of 9,834    |
|    Jim Moseley to All    |
|    Re: Query directly from secondary index    |
|    18 Oct 07 08:05:38    |
      From: jmose@mapson.attglobal.net              Steven,              >but then you'd need to do a 2nd query to grab the remaining       >info you'll need, from the main table..              My app handles this already. In this routine, all I need is a table containing       the 'Key' values. If there is more than one row, I show the user a screen       asking them to choose. Its DM has the Answer.db linked 1-1 to Customer.db       (to show other descriptive fields).              >and, FWIW, you're still doing a dot-dot query,       >that has to go thru all records..              Exactly my point. By directly querying the Customer.XG1 file, I avoid querying       Customer.DB. Since the XG1 only has 2 columns, it should be much faster       than going after my 'wide' tables.              Thanks,       Jim Moseley              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca