One of our guys ran into this recently on a new ASE install, with
new PB5 clients and some old 16-bit PB4 stuff. We saw all kinds of
troubles when the both the 16-bit and 32-bit client software was
installed on a PC with NT 4.0. The problem:
The 16-bit and 32-bit clients were trying to use
different character encodings.
In our case, the 32-bit was set for iso_1 while the 16-bit was
trying to use roman-8 (mixed HP Unix and Wintel NT environment).
We addressed it by making sure that all servers involved had
both character sets installed. It was easier than trying to
reconfigure the several hundred client systems.
If this is helpful to others, I would like to hear. Thanks.
> Installing both sets of drivers has caused clients problems in the past due to
> transport protocol errors..... A real problem to get to the bottom of.
> > Yes,
> > You can install both the 16 and 32 bit drivers in the same directory
> > (/sybase/dll is the default). Both 16 and 32 bit applications work without
> > problems in this environment.
> > >Since Sybase uses the shell variable SYBASE to determine where to find the
> > >Open Client dlls, what do you do if you have to run both apps on the same
> > >machine? In other words one app is a 16-bit app that needs the 16-bit Open
> > >Client dlls, and another app expects the 32 bit dlls. Do I have to
> > comingle
> > >the dlls in the /bin directory?
Richard Scranton, LDA Systems - <http://www.netcom.com/~scrantr/>