Hi there... Here's a doozy for you advanced database gurus...
I have an environment where we are attempting to run a program that uses a Sybase SQL backend for data, except that through a consolidation we are trying to put 4 copies of the same program on a terminal server. Everything works great, except that the FIRST person that logs onto the server determines which database is to be used by each successive person, until that first person logs off the server.
I know, it's wild.
ODBC name is SBS32
ODBC path is Z:\..\sbs32.db
Clients have a virtual drive (z
that "sets up" the z: drive before the program starts, starts the program, then tears down the drive when it's done.
If I go in one user at a time, it will switch between databases just fine. If I log on user 1 to database 1 and user 2 to database 2, user 2 will get database 2 until user 1 logs off... It's nuts.
Any ideas? I need to maintain database compatability with version 5.5, so if anyone knows a way around this I would be most grateful...
Thanks,
Ryan
rleestma@infosysintel.com
P.S. ODBC MUST MUST MUST stay the same.
I have an environment where we are attempting to run a program that uses a Sybase SQL backend for data, except that through a consolidation we are trying to put 4 copies of the same program on a terminal server. Everything works great, except that the FIRST person that logs onto the server determines which database is to be used by each successive person, until that first person logs off the server.
I know, it's wild.
ODBC name is SBS32
ODBC path is Z:\..\sbs32.db
Clients have a virtual drive (z
that "sets up" the z: drive before the program starts, starts the program, then tears down the drive when it's done. If I go in one user at a time, it will switch between databases just fine. If I log on user 1 to database 1 and user 2 to database 2, user 2 will get database 2 until user 1 logs off... It's nuts.
Any ideas? I need to maintain database compatability with version 5.5, so if anyone knows a way around this I would be most grateful...
Thanks,
Ryan
rleestma@infosysintel.com
P.S. ODBC MUST MUST MUST stay the same.