[AccessD] Ascending/Descending Indexes - Retrying

If you have already indexed the field, you don't need another index
defined.  Just change the direction of the sort in code.

Charlotte Foust


-----Original Message-----
From: Andy Lacey [mailto:andy at minstersystems.co.uk] 
Sent: Monday, February 21, 2005 7:45 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Ascending/Descending Indexes - Retrying


Trying again. I'm sure the answer's out there.

--
Andy Lacey
http://www.minstersystems.co.uk



--------- Original Message --------
From: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Subject: [AccessD] Ascending/Descending Indexes
Date: 21/02/05 12:31

>
> Anyone know the answer to this to save me doing a bunch of tests?
>
> If you need to browse a table in descending order of a field (a date 
> in my
> case) and there's an index on that field but defined as ascending
(needed
> elsewhere so can't be changed) is there any benefit from defining a
second,
> descending index on the same field?
>
> --
> Andy Lacey
> http://www.minstersystems.co.uk
>
>
> ________________________________________________
> Message sent using UebiMiau 2.7.2
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
>
>
>

________________________________________________
Message sent using UebiMiau 2.7.2

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com