You can already make temporary indexes using AdsCreateIndex. I use this technique to allow the end user to build runtime filter indexes on data that is constantly shared. When the user closes the index, it deletes the index file that was created. A new one is created each time a user creates a new filter.
I do not know what is so daft about considering that VFP has had this feature for years and I have not experienced data corruption because of it. Reindexing is a different matter and requires exclusive use.
Daft idea. You could easily compromise index integrity. If others are allowed to update the database while the index is being built, and those updates are also trying to update the index because they affect the fields used in the index order, then there could be problems, especially if they occur in the same index page simultaneously.
graphicequaliser
You can already make temporary indexes using AdsCreateIndex. I use this technique to allow the end user to build runtime filter indexes on data that is constantly shared. When the user closes the index, it deletes the index file that was created. A new one is created each time a user creates a new filter.
srwhite
I do not know what is so daft about considering that VFP has had this feature for years and I have not experienced data corruption because of it. Reindexing is a different matter and requires exclusive use.
graphicequaliser
Daft idea. You could easily compromise index integrity. If others are allowed to update the database while the index is being built, and those updates are also trying to update the index because they affect the fields used in the index order, then there could be problems, especially if they occur in the same index page simultaneously.
joachimd
and reindex, please
LePrince
Including FTS indixes, please.