Leonard Berkowitz writes:

>I understand the difference between CIUPDATE=ON and CIUPDATE=ALLOWED (a
call to
>DBCONTROL mode 5). Can someone provide a scenario where the distinction is
>significant? After all the same program[mer] can convert CIUPDATE=ALLOWED
to
>CIUPDATE=ON.

It is only significant when you have older programs that rely on Image to 
*not* allow critical item updates; that is, it was part of the program 
design to rely on an Image "feature" instead of doing the checking itself. 
In this case, enabling global CIUPDATE via the CIUPDATE=ON setting will 
cause such programs to malfunction by performing a DBUPDATE when they used 
to fail.

If you're not sure if you have any programs that fall into that category, 
then you can do what we did and use CIUPDATE=ALLOWED.  Then you can code 
new programs (or update older ones) to use the new CIUPDATE functionality 
by enabling it via the DBCONTROL intrinsic.

Jim Phillips                            Manager of Information Systems
E-Mail: [log in to unmask]      Therm-O-Link, Inc.
Phone: (330) 527-2124                   P. O. Box 285
  Fax: (330) 527-2123                   Garrettsville, Ohio  44231