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