What indexes does your driver use? Does it use the CDX file in Visual Fox Pro?
I thought it did, but yesterday I went into VFP while our system was live and opened a table exclusive and reindexed the file. System users were still able to access their data while the reindex was occurring, even though the reindex took 15 minutes. If your driver was using the VFP tables and indexes, it would have prevented this type of access while the table was in exclusive mode.
Our speed performance is poor. (We are using your driver with Cold Fusion) It appears the VFP Rushmore indexes are not being used!!??
Thanks for your help.
Paul Hall
|
>What indexes does your driver use?
It supports IDX, CDX, NDX, MDX, NTX, and CGP.
>Does it use the CDX file in Visual Fox Pro?
Supports.
>but yesterday I went into VFP while our system was live and opened a table
>exclusive and reindexed the file. System users were still able to access their
>data while the reindex was occurring, even though the reindex took 15 minutes.
>If your driver was using the VFP tables and indexes, it would have prevented
>this type of access while the table was in exclusive mode.
You should use lockType=VFP connection. Then HXTT DBF wil see exclusive lock from VFP, and throw a timeout exception.
>Our speed performance is poor.
>It appears the VFP Rushmore indexes are not being used!!??
Rushmore need many memory, and is MS' patent. HXTT DBF will utilize all index files and temporary index to quicken your query. What's your sql, and what's the record count of your table?
BTW, v4.2.052 fixed an insert bug on CDX index since v4.2.039. Please download it.
|
Main
webmaster@hxtt.com