> Steve,
>
> There are enormous differences between the way that VFP handles indexes and the way server databases do. You really cannot extrapolate from one to the other. Apart from anything else indexes in Database Servers are ONLY for optimizing queries - you don't (and can't) use an index to sort data for display.
>
> [1] I doubt that the instructor was talking rubbish. I also doubt that he/she said 'create a compound index' because as far as I know you cannot do that in Oracle (or SQL Server for that matter). What may have been said was to create a single index that contains multiple columns in the order in which you use them in queries.
>
> [2] No, - at least, you cannot create compound indexes without concatenating columns, which means converting them to the same data type. In SQL you can define an index as:
>
CREATE INDEX acct_sch ON ACCOUNT ( customer, account, invoicedate)
> and it would be usable for single, or multiple, column based queries. But in VFP you would have to build a compound key like:
>
INDEX ON customer+STR(account)+DTOS(invoicedate) TAG acct_sch
> and it would only be usable with concatenated strings or partial strings. So in VFP you are probably better off to stick to single column tags in your indexes (i.e. build a cdx with three tags, one each for customer, account and date)
>
> [3] SQL Server behaves much like Oracle.
>
>
> Regards
> Andy Kramek
> Microsoft MVP (Visual FoxPro)
>
Tightline Computers Inc, Akron Ohio, USAHeya Andy,
Hows things! Any plans to be over this side of the pond this year? Was hoping you would chime in as I know you worked with Oracle.
Thanks for the input
Steve Dingle
http://weblogs.foxite.com/SteveDingle/