By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,705 Members | 1,777 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,705 IT Pros & Developers. It's quick & easy.

Access 97 RunTime & Terminal Services

P: n/a
We have numerous Access 97 apps that we run on our Terminal Server,
but two apps in particular is giving us a problem. The problem we are
running into is when you select a drop down menu, it errors out saying
the SQL server cannot be found. This is through the terminal session
and when logged on the server locally.

If I run the apps on my workstation they work fine.

In one of the problem apps, it runs flawless except for a similar
problem when a drop down menu doesnt work and throws and error about
not being able to connect to the SQL Server. All the other dropdown
menus (driven by a SQL Query as well) work fine.

The problem is reproducible every time, but its only on these two
particular drop down menus in these two apps.

I uninstalled and reinstalled the Access 97 runtime. I rebooted the
server. I ran Process Monitor, Network Monitor, etc and looked for any
errors with permissions and nothing popped up.

I built a similar system and the apps run fine through terminal
sessions on that box, but not on the deployed Terminal server.

Any ideas? I dont want to rebuild the box if I dont have to.

Thanks,
--Mike

Aug 8 '07 #1
Share this Question
Share on Google+
7 Replies


P: n/a

<mi**@mcarlson.netwrote in message
news:11*********************@w3g2000hsg.googlegrou ps.com...
We have numerous Access 97 apps that we run on our Terminal Server,
but two apps in particular is giving us a problem. The problem we are
running into is when you select a drop down menu, it errors out saying
the SQL server cannot be found. This is through the terminal session
and when logged on the server locally.

If I run the apps on my workstation they work fine.

In one of the problem apps, it runs flawless except for a similar
problem when a drop down menu doesnt work and throws and error about
not being able to connect to the SQL Server. All the other dropdown
menus (driven by a SQL Query as well) work fine.

The problem is reproducible every time, but its only on these two
particular drop down menus in these two apps.

I uninstalled and reinstalled the Access 97 runtime. I rebooted the
server. I ran Process Monitor, Network Monitor, etc and looked for any
errors with permissions and nothing popped up.

I built a similar system and the apps run fine through terminal
sessions on that box, but not on the deployed Terminal server.

Any ideas? I dont want to rebuild the box if I dont have to.

Thanks,
--Mike
If it was a Jet back end, I would verify the path to the MDB when logged-on
the terminal server. Can you use the same connection information in excel on
the terminal server?
Aug 8 '07 #2

P: n/a
On Aug 8, 4:22 pm, "paii, Ron" <n...@no.comwrote:
<m...@mcarlson.netwrote in message

news:11*********************@w3g2000hsg.googlegrou ps.com...
We have numerous Access 97 apps that we run on our Terminal Server,
but two apps in particular is giving us a problem. The problem we are
running into is when you select a drop down menu, it errors out saying
the SQL server cannot be found. This is through the terminal session
and when logged on the server locally.
If I run the apps on my workstation they work fine.
In one of the problem apps, it runs flawless except for a similar
problem when a drop down menu doesnt work and throws and error about
not being able to connect to the SQL Server. All the other dropdown
menus (driven by a SQL Query as well) work fine.
The problem is reproducible every time, but its only on these two
particular drop down menus in these two apps.
I uninstalled and reinstalled the Access 97 runtime. I rebooted the
server. I ran Process Monitor, Network Monitor, etc and looked for any
errors with permissions and nothing popped up.
I built a similar system and the apps run fine through terminal
sessions on that box, but not on the deployed Terminal server.
Any ideas? I dont want to rebuild the box if I dont have to.
Thanks,
--Mike

If it was a Jet back end, I would verify the path to the MDB when logged-on
the terminal server. Can you use the same connection information in excel on
the terminal server?
Its a SQL Server backend. While logged onto the terminal server, the
other Access apps with SQL Backends work fine. In fact, one app has no
problem at with data exchange except for one drop down menu. The app
works fine until you get a specific for with a drop down menu.

Aug 9 '07 #3

P: n/a

<mi**@mcarlson.netwrote in message
news:11**********************@w3g2000hsg.googlegro ups.com...
On Aug 8, 4:22 pm, "paii, Ron" <n...@no.comwrote:
<m...@mcarlson.netwrote in message

news:11*********************@w3g2000hsg.googlegrou ps.com...
We have numerous Access 97 apps that we run on our Terminal Server,
but two apps in particular is giving us a problem. The problem we are
running into is when you select a drop down menu, it errors out saying
the SQL server cannot be found. This is through the terminal session
and when logged on the server locally.
If I run the apps on my workstation they work fine.
In one of the problem apps, it runs flawless except for a similar
problem when a drop down menu doesnt work and throws and error about
not being able to connect to the SQL Server. All the other dropdown
menus (driven by a SQL Query as well) work fine.
The problem is reproducible every time, but its only on these two
particular drop down menus in these two apps.
I uninstalled and reinstalled the Access 97 runtime. I rebooted the
server. I ran Process Monitor, Network Monitor, etc and looked for any
errors with permissions and nothing popped up.
I built a similar system and the apps run fine through terminal
sessions on that box, but not on the deployed Terminal server.
Any ideas? I dont want to rebuild the box if I dont have to.
Thanks,
--Mike
If it was a Jet back end, I would verify the path to the MDB when
logged-on
the terminal server. Can you use the same connection information in
excel on
the terminal server?

Its a SQL Server backend. While logged onto the terminal server, the
other Access apps with SQL Backends work fine. In fact, one app has no
problem at with data exchange except for one drop down menu. The app
works fine until you get a specific for with a drop down menu.
Does the drop down menu use the same connection string as the rest of the
app?
Aug 9 '07 #4

P: n/a
On Aug 8, 4:22 pm, "paii, Ron" <n...@no.comwrote:
<m...@mcarlson.netwrote in message

news:11*********************@w3g2000hsg.googlegrou ps.com...
We have numerous Access 97 apps that we run on our Terminal Server,
but two apps in particular is giving us a problem. The problem we are
running into is when you select a drop down menu, it errors out saying
the SQL server cannot be found. This is through the terminal session
and when logged on the server locally.
If I run the apps on my workstation they work fine.
In one of the problem apps, it runs flawless except for a similar
problem when a drop down menu doesnt work and throws and error about
not being able to connect to the SQL Server. All the other dropdown
menus (driven by a SQL Query as well) work fine.
The problem is reproducible every time, but its only on these two
particular drop down menus in these two apps.
I uninstalled and reinstalled the Access 97 runtime. I rebooted the
server. I ran Process Monitor, Network Monitor, etc and looked for any
errors with permissions and nothing popped up.
I built a similar system and the apps run fine through terminal
sessions on that box, but not on the deployed Terminal server.
Any ideas? I dont want to rebuild the box if I dont have to.
Thanks,
--Mike

If it was a Jet back end, I would verify the path to the MDB when logged-on
the terminal server. Can you use the same connection information in excel on
the terminal server?
Its a SQL Server backend. While logged onto the terminal server, the
other Access apps with SQL Backends work fine. In fact, one app has no
problem at with data exchange except for one drop down menu. The app
works fine until you get a specific for with a drop down menu.

Aug 9 '07 #5

P: n/a
On Aug 9, 8:21 am, "paii, Ron" <n...@no.comwrote:
<m...@mcarlson.netwrote in message

news:11**********************@w3g2000hsg.googlegro ups.com...
On Aug 8, 4:22 pm, "paii, Ron" <n...@no.comwrote:
<m...@mcarlson.netwrote in message
>news:11*********************@w3g2000hsg.googlegro ups.com...
We have numerous Access 97 apps that we run on our Terminal Server,
but two apps in particular is giving us a problem. The problem we are
running into is when you select a drop down menu, it errors out saying
the SQL server cannot be found. This is through the terminal session
and when logged on the server locally.
If I run the apps on my workstation they work fine.
In one of the problem apps, it runs flawless except for a similar
problem when a drop down menu doesnt work and throws and error about
not being able to connect to the SQL Server. All the other dropdown
menus (driven by a SQL Query as well) work fine.
The problem is reproducible every time, but its only on these two
particular drop down menus in these two apps.
I uninstalled and reinstalled the Access 97 runtime. I rebooted the
server. I ran Process Monitor, Network Monitor, etc and looked for any
errors with permissions and nothing popped up.
I built a similar system and the apps run fine through terminal
sessions on that box, but not on the deployed Terminal server.
Any ideas? I dont want to rebuild the box if I dont have to.
Thanks,
--Mike
If it was a Jet back end, I would verify the path to the MDB when
logged-on
the terminal server. Can you use the same connection information in
excel on
the terminal server?
Its a SQL Server backend. While logged onto the terminal server, the
other Access apps with SQL Backends work fine. In fact, one app has no
problem at with data exchange except for one drop down menu. The app
works fine until you get a specific for with a drop down menu.

Does the drop down menu use the same connection string as the rest of the
app?
Yes, its just a query from a linked table. The app contains a dozen or
so linked tables and a couple local tables to write error stuff to.

Sorry about the double post, Google groups kept throwing up an error
so I kept resubmitting it.

Aug 9 '07 #6

P: n/a

<mi**@mcarlson.netwrote in message
news:11*********************@d55g2000hsg.googlegro ups.com...
On Aug 9, 8:21 am, "paii, Ron" <n...@no.comwrote:
<m...@mcarlson.netwrote in message

news:11**********************@w3g2000hsg.googlegro ups.com...
On Aug 8, 4:22 pm, "paii, Ron" <n...@no.comwrote:
<m...@mcarlson.netwrote in message
news:11*********************@w3g2000hsg.googlegrou ps.com...
We have numerous Access 97 apps that we run on our Terminal
Server,
but two apps in particular is giving us a problem. The problem we
are
running into is when you select a drop down menu, it errors out
saying
the SQL server cannot be found. This is through the terminal
session
and when logged on the server locally.
If I run the apps on my workstation they work fine.
In one of the problem apps, it runs flawless except for a similar
problem when a drop down menu doesnt work and throws and error
about
not being able to connect to the SQL Server. All the other
dropdown
menus (driven by a SQL Query as well) work fine.
The problem is reproducible every time, but its only on these two
particular drop down menus in these two apps.
I uninstalled and reinstalled the Access 97 runtime. I rebooted
the
server. I ran Process Monitor, Network Monitor, etc and looked for
any
errors with permissions and nothing popped up.
I built a similar system and the apps run fine through terminal
sessions on that box, but not on the deployed Terminal server.
Any ideas? I dont want to rebuild the box if I dont have to.
Thanks,
--Mike
If it was a Jet back end, I would verify the path to the MDB when
logged-on
the terminal server. Can you use the same connection information in
excel on
the terminal server?
Its a SQL Server backend. While logged onto the terminal server, the
other Access apps with SQL Backends work fine. In fact, one app has no
problem at with data exchange except for one drop down menu. The app
works fine until you get a specific for with a drop down menu.
Does the drop down menu use the same connection string as the rest of
the
app?

Yes, its just a query from a linked table. The app contains a dozen or
so linked tables and a couple local tables to write error stuff to.

Sorry about the double post, Google groups kept throwing up an error
so I kept resubmitting it.
The query is not a pass-though?

Can you add a form or report, based on the query and open it on the terminal
server?

Are you using runtime on your workstations or only on the terminal server.
If not test the application using the runtime switch on your workstation.
Aug 9 '07 #7

P: n/a
mi**@mcarlson.net wrote:
>In one of the problem apps, it runs flawless except for a similar
problem when a drop down menu doesnt work and throws and error about
not being able to connect to the SQL Server. All the other dropdown
menus (driven by a SQL Query as well) work fine.
>The problem is reproducible every time, but its only on these two
particular drop down menus in these two apps.
This, of course, makes absolutely no sense at all. That said is there anything
unique about those combo boxes? Are they doing something wierd and using a call back
function? Could you post the contents of the Control Source field.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Aug 15 '07 #8

This discussion thread is closed

Replies have been disabled for this discussion.