|
Main reason is cost of license. I have a site license for a basic 5250 client that has all the functionality that 99% of my user community needs. Client access is overkill and costs too much to deploy to everyone. I would like to get ODBC access without having to put all the other "stuff" on a machine. > -----Original Message----- > From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] > Sent: Thursday, April 21, 2005 9:48 AM > To: Midrange Systems Technical Discussion > Subject: RE: Access iSeries from windows and odbc question > > There are probably good reasons not to load the full version but I want to > make sure they're the right reasons for you. > If you just don't want to eat up that much disk space on your PC's I can > understand this on older PC's, but newer ones shouldn't be an issue. > But, if it's because the thought of users getting all those cool tools of > iSeries access causing you some security concerns; that is not a valid > reason. All it takes is one person loading it from somewhere to get > access. Better to secure who can do what with: > - iSeries Access "Application Administration" > - Exit point programs > - "Application Only" access. Which basically means that the only way to > access data is with programs that adopt authority. Which poses some > challenges (although not insurmountable) to an ODBC shop. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > "Mitchell, John" <jmitchell@xxxxxxxxxxxxx> > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 04/21/2005 09:40 AM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > > To > "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > cc > > Subject > RE: Access iSeries from windows and odbc question > > > > > > > Is there any way to get the ODBC driver separated from Client Access? I > would like to use it but I don't want to install the full version to get > just that portion. > > Thanks in advance for any help! > > > -- > 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.