Re: ODBC and MS Access as a security exposure

Jay, Vernon,

that was it.  the driver was set for read uncommitted, not none.

thanks!

Rick


On Thu, 31 Mar 2005 08:48:16 -0500, Himes, Jay <jehimes@xxxxxxxxxxx> wrote:
> Also, you need to check the journaling status of the file vs the
> commandment control setting in the ODBC connection. If commitment
> control is set to anything but *NONE the file must be journal led.
> 
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rick baird
> Sent: Wednesday, March 30, 2005 7:41 PM
> To: Midrange Systems Technical Discussion
> Subject: ODBC and MS Access as a security exposure
> 
> Hey all,
> 
> We're in the process of locking down such things, and the natives are
> restless, and the crew is becoming mutinous (the power users are
> complaining).
> 
> on green screen, we've got no problem - all the users have access to
> is the application (no command line).   But some of our power users
> access DB2/400 tables via MS Access
> 
> I have always operated under the assumption that if a user has *CHANGE
> authority to a file, he could use a product such as MS Access to change
> the data in a DB2/400 file via "linked tables" and ODBC.
> 
> I tested this, and it appears I'm wrong.  It errors out when I try to
> change the linked table.  (I have *ALL access to the file).
> 
> What am I missing?
> 
> Thanks,
> 
> Rick
> --
> 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.
> 
> --
> 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.
> 
>