RE: Logical File - How to Deny SQL Deletes??

Jim,

Are you specifying the logical file itself in the from clause of the SQL?

If yes, then the object security on the LF should have the correct effect.

Unless the web server is logging on under some profile with *ALLOBJ (which
would be a big no-no)

Charles


> -----Original Message-----
> From: Trow, Jim [mailto:J.Trow@xxxxxxxxxxxxx]
> Sent: Thursday, October 07, 2004 11:47 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Logical File - How to Deny SQL Deletes??
> 
> 
> Good morning,
> 
>  
> 
> I would like to provide our web server direct access to our AS/400
> production data via SQL server commands, but at the same time 
> have that
> access controlled and restricted to read-only so that 
> database integrity
> remains intact.   I've created a logical file based on the physical
> file(s) in question, and have tried numerous combinations of object
> authority changes on both the logical file and user profile 
> used by the
> web server in order to test against SQL Deletes coming from the web
> server and nothing has worked.
> 
>  
> 
> I'm surprised to have not found anything relating to this in the
> archives, and am wondering if I'm completely missing an easier or more
> accepted approach to my issue.  Does anyone have any ideas or
> suggestions?
> 
>  
> 
>  
> 
> Thanks,
> 
> Jim
> 
>  
> 
> James D. Trow
> 
> Information Systems Supervisor
> 
> Dick Blick Holdings, Inc.
> 
> Ph: (847) 681-6820
> 
> Cell: (847) 309-4760
> 
> Email:  <mailto:tj.trowj@xxxxxxxxxxxxx> J.Trow@xxxxxxxxxxxxx
> 
>  
> 
> --
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>