OI 3.7

Win95

We have a client who is running a single user version of our OI application. We have background indexing turned on for them, that is we have the "Seconds Before Update" field in the Database Manager Environment settings set to a number (which eludes me at the momement) and we have the "Update Before Query" field checked in the same window.

The user is having a problem running a report that selectes records from an indexed table. They will add transactions and run the report but the new transactions will not show up on the report unless they rebuild the indexes on that table?

Does this mean that the "Seconds Before Indexing" field is set to high or is there some other explantion??? I am worried that if I set this number too low the system will slow down too much.

It is not practical to have a dedicated indexing machine as they only have a single user.

Thanks,

Michael

Michael,

I gave up on background indexing a long time ago. Instead I have index update code in all my data entry windows' WRITE handlers.

I remember I had one particular table with approximately 25 indexes. I found that background indexing updated only one index at a time. So with background indexing set to n seconds it took n*25 seconds to finish. OK if your users take a coffee break for each row, otherwise not.

Also it wasn't as realiable as programmatic update (even with coffee breaks). E.g sometimes indexes got stuck, and wouldn't let themselves be updated. (At least I think background indexing had a finger in that.) I notice you say "unless they rebuild the indexes" and not "unless they update the indexes". Does it mean your indexes get stuck, and won't update?

- Oystein -

A bit late but…

The best way seems to be running one more copy of AREV on the same machine to be used as a dedicated indexer process.

Aaron "said" it is OK to run two processes on the same station (Ask him whether the configuration is right).

You must be a bit careful to set different parameters for indexing.

For such purposes use

SET AREV=INDEX.INI in the startup batch for the indexing process to distinguish the "parameter" files.

(Muster .INI files are in the AREV directory)

Oh sorry, I didn't read it well… it is OI …

View this thread on the forum...