>Is there any way to specify a location for a table's structural .CDX file that's different from the table's location?
>
>I'd like to tweak the performance of a VFP app by using an SQL Server trick: putting the index file on a different drive. I know this can work for a non-structured .CDX, but I'd like to try it with the table's main structured .CDX.
>
>I tried moving a structural .CDX to it's new location and reassociating it with it's table by issuing:
>
> USE myTable INDEX [Different Drive:\Path]\myTable.CDX
>
>But when I closed it and reissued USE without the INDEX option, I got the "Cannot Locate Index" error.(I also retried the above and issued REINDEX, still no dice)
>
>I'm just wondering if there's a .DBC hack or something that would make this possible.
>
>Thanks,
>
>-Bernie

why not just use the SET ORDER TO command in your code to set the structural CDX that you want to use right after you open the table?
i tried to play around with the property memo field in the DBC when VFP first came out but i just settled for the above method.

I have used the trick of placing the index file and the table data on different physical drives and on 5 year old hardware SEEK times decreased by about 20 percent, but on our new hard drives (scsi ultra fast and whatever) performance did not change. I used index files between 125MB and 400MB.

HTH, Dave.