filepro question

[Walter Vaughan Jr]

Well, the smart answer would be to fix whatever you think is breaking your indexes. I get that in a Windows environment, indexes could get wonky, but in a *nix world, that's something that should really never happen.

However, you (or someone well compensated) could put together a shell script that would
1) check to make sure no one is running filePro
2) lock out everyone from using filePro
3) delete all the indexes in question
4) run your delete processes
5) rebuild indexes
6) allow others to use filePro

I do worry however, that you think you can move an index back in safely after deleting or adding records in a multiuser environment.

I'd spend the time and money fixing the index problem, rather than working around it.




-----Original Message-----
From: Filepro-list [mailto:filepro-list-bounces+wvaughan=steelerubber.com at lists.celestial.com] On Behalf Of davidrottkamp via Filepro-list
Sent: Thursday, January 04, 2018 3:03 PM
To: filepro <filepro-list at lists.celestial.com>
Subject: filepro question

Hi


Linux Red Hat
filepro

Does any one know of a flag or way to have rreport run without trying to rebuild indexes if you delete records in pother words turn off indexing temporarily so I may delete a ton of records without index errors

than I would rebuild indexes after the fact I know I could move indexes out temporarily and than back and re-index but I want an alternate method if there is one

--
*David Rottkamp