Hi there,
in the company I work in, we´re using a software which is based on Gupta SQLBase 9.01. We´re using the software on a Windows 2003 Terminal Server.
To be able to generate reports with Microsoft Access, we were given the SYSADM account and password for the Gupta database.
Now, if I create a new system ODBC connection on the Terminal Server two things happen:
1) The ODBC connection works. I can generate reports with MS Access.
2) The software mentioned above loses its connection to the database and can´t reconnect until i delete the ODBC connection.
That is really annoying. Is there any way to get around this? We won´t be able to work with local PCs much longer, since everything is upgraded to a thin client environment...
Any help would be greatly appreciated!
Aleks
in the company I work in, we´re using a software which is based on Gupta SQLBase 9.01. We´re using the software on a Windows 2003 Terminal Server.
To be able to generate reports with Microsoft Access, we were given the SYSADM account and password for the Gupta database.
Now, if I create a new system ODBC connection on the Terminal Server two things happen:
1) The ODBC connection works. I can generate reports with MS Access.
2) The software mentioned above loses its connection to the database and can´t reconnect until i delete the ODBC connection.
That is really annoying. Is there any way to get around this? We won´t be able to work with local PCs much longer, since everything is upgraded to a thin client environment...
Any help would be greatly appreciated!
Aleks