>What mode are you in? Updating CIs require mode 1, 3, or 4.
>
>Check your TurboImage manual on this value. There are three settings for
>CIUpdate: OFF, ON, and ALLOWED. I prefer allowed, but it does require another
>call to enable it before the CIUpdate, and another to disable it when you're
>finished. Think of it as a safety; it is hard to do accidentally update a key
>this way, whereas with ON, anyone can update a key anywhere at anytime.
>
>From the manual:
>The ALLOWED setting
>requires that a process first call DBCONTROL in mode 5 to enable the
>CIUPDATE option for the duration of the process or until a call to
>DBCONTROL in mode 6 disables the option.  Using DBCONTROL modes 5 and 6
>does not alter the permanent setting set with the DBUTIL >>SET command.
>The database must be opened in access mode 1, 3, or 4; and your user
>class must have write access at the set level, or both read access at the
>set level and write access at the item level.
>
>----------
>From:  Jesus Valdez[SMTP:[log in to unmask]]
>Sent:  Thursday, November 21, 1996 6:19 PM
>To:    [log in to unmask]
>Subject:       CIUPDATE problem
>
>Fellow listers:
>I'm trying to change(update) via QUERY the value of a critical item (key)
>in a TurboImage database. First thing I tried was DBUTIL with this
>command:
>                  SET database name CIUPDATE = ALLOWED
>and sure enough I got:
>>> CIUPDATE is allowed.
>
>However, when I run QUERY with the REPLACE command, I still get this
>message:
> DBUPDATE attempted to modify value of critical item--key, search or sort
>
>0 OF 1 QUALIFYING ENTRIES REPLACED
>
>I need some help. All replies will be appreciated. Thanks.
>
>