RE: Using a .udl file on Windows to set up an OLE DB connection

["Wilt, Charles" <CWilt@xxxxxxxxxxxx>]

Martin,

I've set one up before and just left the initial catalog blank.

It's not of much help if you're pulling from multiple libraries anyway.

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Martin Rowe
> Sent: Monday, June 13, 2005 5:22 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Using a .udl file on Windows to set up an OLE DB 
> connection
> 
> 
> On 13/06/05, Jeff Glenn <jeff.glenn@xxxxxxxxxxxxxxxxxxx> wrote:
> > Martin,
> > 
> > I recently used a udl file for the first time. If you 
> haven't already
> > done this, you can create an empty file in notepad with a 
> udl extension
> > and then double-click it. It will launch the Data Link Properties
> > window where you define the connection, provider, etc.
> 
> Hi Jeff
> 
> I've got that far - I just don't know what needs putting in next! I
> select the iSeries DB2 OLE DB as provider, and set the system I'm
> connecting to. It then prompts for catalog, but any combination of
> library and/or file results in errors testing the connection (with a
> valid user id/passwd).
> 
> Regards, Martin
> -- 
> martin@xxxxxxxxxx  AIM/Gaim: DBG400dotNet  http://www.dbg400.net   /"\
> DBG/400 - AS/400 & iSeries Open Source/Free Software utilities     \ /
> Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news   X
>                                                                    / \
> 
> -- 
> 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.
> 
>