Access 95 ODBC problems over terminal services

[Mike B.]

We have an Access 95 database that has a set of linked
tables via an ODBC to our SQL 2000 SP3 server.

When I open up a terminal services session (via Citrix),
I'm able to define my ODBC conncetion through Control
Panel->Administrative Tools->ODBC Data Sources. I make
sure the ODBC connection is ok - it even tests out ok.

As soon as I open up Access 95 and attempt to use that
particular ODBC connection, I get the following error:

Connection failed:
SQLState: "01000"
SQL Server Error: 10093
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
ConnectionOpn )Initialize()()).
Connection failed:
SQL State: "08001"
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General
network error. Check your network documentation.

A few things I've tried (and notes):

1. I can ping the SQL server by both name and ip address
2. Both citrix server and SQL Server are on the same
subnet.
3. I am logged on as an Administrator thorughout this.
4. Using the same ODBC Data Source through Access 2000 to
link tables works perfectly.

I'm believing it's something to do with the ODBC
drivers/libraries Access 95 is using - perhaps they're not
compatible with Terminal Services.

Unfortunately, our Access Database has A LOT of VBA code
written for Access 95 that cannot be easily upgraded to
Access 2000, so we're trying to find a work around.

Any ideas out there?

 

[david epsom dot com dot au]

Unfortunately, our Access Database has A LOT of VBA code

written for Access 95 that cannot be easily upgraded to

DAO 2.5 code? There was very little of our A97 code
that needed to be changed after the conversion from
Access 2.0 was complete. Mostly recursive DAO calls
and exception handling that caused A2K to fault. A few
problems with parameter queries.

(david)

We have an Access 95 database that has a set of linked
tables via an ODBC to our SQL 2000 SP3 server.

When I open up a terminal services session (via Citrix),
I'm able to define my ODBC conncetion through Control
Panel->Administrative Tools->ODBC Data Sources. I make
sure the ODBC connection is ok - it even tests out ok.

As soon as I open up Access 95 and attempt to use that
particular ODBC connection, I get the following error:

Connection failed:
SQLState: "01000"
SQL Server Error: 10093
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
ConnectionOpn )Initialize()()).
Connection failed:
SQL State: "08001"
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General
network error. Check your network documentation.

A few things I've tried (and notes):

1. I can ping the SQL server by both name and ip address
2. Both citrix server and SQL Server are on the same
subnet.
3. I am logged on as an Administrator thorughout this.
4. Using the same ODBC Data Source through Access 2000 to
link tables works perfectly.

I'm believing it's something to do with the ODBC
drivers/libraries Access 95 is using - perhaps they're not
compatible with Terminal Services.

Unfortunately, our Access Database has A LOT of VBA code
written for Access 95 that cannot be easily upgraded to
Access 2000, so we're trying to find a work around.

Any ideas out there?

 

[Tony Toews]

Unfortunately, our Access Database has A LOT of VBA code
written for Access 95 that cannot be easily upgraded to
Access 2000, so we're trying to find a work around.

I'd have to echo David's comments. There's some work involved in
converting but not a lot.

I'm wondering if you imported into a new MDB which didn't have the DAO
reference set. Thus making it look like lots of problems.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm