Re: Emulator Interface with Win2k

Maybe the key is to change the ODBC driver but give it the same name as the
current data source. Then the change is in the ODBC config, and maybe VB
can just use it - I'd be looking at any extra stuff, like authentication,
that VB is doing. But if the connection stuff is now completely hidden in
the ODBC data source, you might not need to change anything in the VB code.

At 01:35 PM 3/20/02 -0500, you wrote:
>Vernon,
>
>I am aware of the usual suspects but if you red my original message I have
>some issues with VB programming that's been going on for over 5 years and
>I'm trying to put my finger on how many.  So I need to get a package that
>works with Win2k and one that I won't have to change all my VB codes because
>of ODBC or OLE/DB drivers e.t.c.  I'm aware that some of these packages
>support different version of drivers, ODBC and/or OSes
>
>Dare
>
>----- Original Message -----
>From: "Vernon Hamberg" <vhamberg@attbi.com>
>To: <midrange-l@midrange.com>
>Sent: Wednesday, March 20, 2002 1:06 PM
>Subject: RE: Emulator Interface with Win2k
>
>
> > I agree. Go with native TCP/IP. You get more options, all the usual
> > suspects, like WRQ Reflection, Personal Communications, Synapse, Client
> > Access, NetManage Rumba, various ODBC and OLE/DB drivers, etc.
> >
> > What benefit is there with SNA Server, other than connectivity?
> >
> > At 10:01 AM 3/20/02 -0800, you wrote:
> > >Dare,
> > >
> > >In this day and age, an SNA gateway represents a huge overhead with
> > >unnecessary complexity.  Scrub the hard disk and set it up as a Linux
> > >play pen!
> > >
> > >You'll find your network easier to manage if you remove the gateway and
> > >go direct to the AS/400.
> > >
> > >IMHO
> > >
> > >Best Regards
> > >
> > >Fritz Hayes
> > >Atwater Associates
> > >
> > ><snip>
> > >|
> > >| I forgot about my SNA Server.  All client pass through this server to
> > >get
> > >| to
> > >| the AS/400
> > >|
> > >
> > >_______________________________________________
> > >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>list
> > >To post a message email: MIDRANGE-L@midrange.com
> > >To subscribe, unsubscribe, or change list options,
> > >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > >or email: MIDRANGE-L-request@midrange.com
> > >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@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > 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@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.