> > In the past I have always create indexes on single fields that were going to be part of my WHERE clause, except for fields like boolean or with little varitions in values.
> >
> > I was recently on a beginners course with Oracle and the instructor spent a bit of time talking about indexes and b-tree and was quite adamant that if you had a primary key made up of multiple fields or regularly did searches on a group of fields that to get the best results you should create a compound index using those field and then use that expression in your where clause.
> >
> > With that in mind, say I have a table with Customer,Account,Invoice Date. In the past I would have created individual indexes on these fields and then used a where clause like:
> >
> >

 Customer = 'MyCustomer'
> >  AND Account = 1234
> >  AND Invoice Date = {01/02/2009}
> > 

> >

Another q: VFP imposed a lot of restrictions on ambiguous dates back before the turn of the century. Did that pass unnoticed in the UK? -)

-Anders