🚀 go-pugleaf

On Fri, 27 Feb 1998 17:40:25 -0500, Peter Rorlick <peter@InjuryTracker.com>
wrote:

>Steve Koterski wrote:
>
>> More information, please:
>>
>> What type of local table? dBASE or Paradox? What level table?
>
>dBase level 7.
>
>> What type of index was used? Primary or secondary? Single- or
>> multi-column?
>> dBASE expression index?
>
>Index on Customer_ID tag CustNo
>In other words, to a tag in an MDX.
>BTW what are primary/secondary indexes? I've developed in xbase for 16
>years and I've never encountered that phrase.

<GRIN>
Visual dBASE 7 introduced a number of new features to the dBASE table
format. (Features bringing dBASE tables somewhat up to the '90s.)
</GRIN>

One of the new features is the primary index. Previously, all dBASE indexes
were secondary indexes. Now, you can have a primary index, too. Primary
indexes allow only unique values in the field that compose the index and
are supposed to be uatomatically used as the default sort order for a
table.

My questions were centered mostly on the table type and and whether simple
or compound. My own testing has verified that dBASE simple indexes (which
is what yours is, based on a single field) are used by SELECT queries.
Queries with an ORDER BY clause would ordinarily be read-only, but
existence of an index for the fields in the ORDER BY clause allows the
query to be updatable.

What is your exact SQL statement. I would be looking at the joining fields
and field comparisons in the WHERE clause (if there is one), looking in the
context of the index information you have already provided.

**************************************************************************
Steve Koterski
Borland International, Inc.
http://www.borland.com/delphi
(Remove the "SPICEDHAM2" from the address. Death to spam-bots!)