× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Vern,

Your note sent me searching and I think I've found a good workaround for
this situation. When I start up ODBC Administration in the iSeries Access
for Windows application set, then select my server .... there is a Server
tab that has a box for library list. If you enter a specific library in
this box, it sets that up as your library for reference and no longer uses
the *USRLIBL list.

Turns out we were using the IBM ODBC driver all along.

Rich Loeber
Kisco Information Systems
http://www.kisco.com

--------------------------------------------------------------------------

vhamberg@xxxxxxxxxxx wrote:

Which MS ODBC driver? Is there one for iSeries? It'd be very odd for
Microsoft to provide the ODBC driver for another vendor's database.

Having said that, verify which they are using - it'll be shown in the
DSN - and what Marty suggested should be there in the setup - if not,
get it updated.

If it is HIT's driver, there are bound to be similar controls.

<verndor response>
Actually we have an interesting product - Office Integrator - that works
in the opposite direction - originally intended to replace MailMerge
from OfficeVision - it sends data from iSeries to the PC, then activates
the merge mechanism in Word, all from iSeries CL commands. The usual -
check www.rjssoftware.com or call us at 888.rjs.soft
</verndor response>

HTH
Vern

-------------- Original message --------------
From: Rich Loeber <rich@xxxxxxxxx>

> Thanks Marty. I've been toying with that as a backup solution, but to
have the
> ODBC data request be library specific would be the right way to go, if
we can.
>
> Rich
>
------------------------------------------------------------------------
>
> "Urbanek, Marty" wrote:
>
> > Rich,
> >
> > Could you have them try the iSeries Access ODBC driver? I think that
one
> > lets you define the library list when you set up the data source.
I'm
> > not big into this stuff but that might be something you could try.
> >
> > -Marty
> >
> > ------------------------------
> >
> > date: Thu, 08 Nov 2007 12:40:35 -0500
> > from: Rich Loeber
> > subject: ODBC Connection from Word
> >
> > I have a customer that is using ODBC from within Word (2003) to do a
> > mailmerge with a database file on their system in library QS36F. The
> > connection works just fine, but when it is processed on their
server,
> > it's library reference is *USRLIBL .... this creates a security
issue as
> > it gives the end user access to anything in their library list.
Short
> > of severly restricting their library list, does anyone know how to
make
> > this ODBC request library specific? I've gotten it to work on my
test
> > sandbox, but it still comes up as a *USRLIBL request. It appears
like
> > they are using the MS ODBC driver.
> >
> > Rich Loeber
> > Kisco Information Systems
> > http://www.kisco.com


------------------------------------------------------------------------
--
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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.