index update (OpenInsight 32-bit Specific)
At 04 JAN 2004 01:40:45PM jay rappaport wrote:
would like to know if there is a way to suppress the automatic updating of indexs. have an application where after the data has been entered, the user still wants all indexs to reflect how things looked at the start of the day. I know this might sound odd, since records could be retrived that do not match the current values, but in this case there are offices all over the place, and they want everyone to work from the same set of lists (so to speak).
would like the updating to take place at off hours, during an "overnite' process - which i could setup, the question is can the update of indexs be disabled.
In the alternative, is there a method, following the above, that certain indexes can be set to auto-update, and others not to?
thanks
At 04 JAN 2004 04:30PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Turn off background indexing in the database manager environment settings then use index.flush when you want indexes updated.
World Leaders in all things RevSoft
At 04 JAN 2004 06:13PM jay rappaport wrote:
ok - silly question then -
where or how to you turn off background updating??
is there a magic number to use when setting the delay so that it functionally never happens? did not see an option to disable.
tia
At 04 JAN 2004 08:34PM Donald Bakke wrote:
Jay,
Set the Delay before Indexing to 0 to turn it off. If you are using an index server you might also want to look at the Set_IDXSvr and Set_Bgnd_IX_Time functions.
dbakke@srpcs.com
At 04 JAN 2004 09:59PM jay rappaport wrote:
thank you – guess that zero (0) is the magic number then
would have been nice if that was documented since i could not find it in the online documentation.
At 07 JAN 2004 09:47AM Richard Guise wrote:
1) I thought that even if b'ground index off (e.g. for dedicated index server) certain processes like R/List SELECT automatically flush indexes. Could be hazardous or unreliable?
2) Aren't there any circumstances during the day when some users might want to use up to date info instead of out of date info?
Can you not use the good old "savelists" which would be both reliable and flexible? Some process done first thing to update the savelists. About 20 years ago I had a Pick client whose entire life seemed to be run in this way by savelists!