Was the database you "tested" with already open?  If so, query might "force" you into opening it in a "compatible" mode -- try this with a database that is not being accessed by anyone else.

As to the original question, it generally doesn't matter WHERE the database resides as the IMAGE intrinsics manage access using the "access" words defined in the schema [though the database may have to be "released" for non-privileged users]  If you are worried about arbitrary access via QUERY (and you should be...), you can "disable subsystem access" via DBUTIL.

(of course, any true SM worth his salt can retrieve the DB owner's password, log on as that user, and go to town with the data, but you didn't hear that from me... ;) )

----- Original Message ----
From: "Simpkins, Terry" <[log in to unmask]>

well, I sure thought you could use QUERY to do this if you had an IMAGE
password with update access rights.
But when I just tested that, it seems to 'force' me into Mode 6;
eventhough I specified mode=1.

Strange.

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On

Hi all.
I am going thru an audit.  (Oh yeah!)
Can an SM user update a DB in another account?  I am thinking maybe they
could but would require a DB password. Thanks. Ray







* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *