Hi, I'm running an Access database that's been running for 2 years without problems. I have the backend on a Sequel2000 Server and never had any problems with it. I now swapped out the computer with a thin client running Terminal Services. I was using Access 2000 and the problem is that the thin client access application keeps locking up. The mouse click seems to stop working for the access application. Is there something special I must do to use this database in a terminals service session? I ended up making it an MDE thinking this would help, but it didn't seem to change anything. I only have (2) users using the database, (1) being a PC and the other a thin client. The PC doesn't have this problem.
> Hi, I'm running an Access database that's been running for 2 years without > problems. I have the backend on a Sequel2000 Server and never had any > problems with it. I now swapped out the computer with a thin client > running > Terminal Services. I was using Access 2000 and the problem is that the > thin > client access application keeps locking up. The mouse click seems to stop > working for the access application. Is there something special I must do > to > use this database in a terminals service session? > I ended up making it an MDE thinking this would help, but it didn't seem > to > change anything. I only have (2) users using the database, (1) being a PC > and > the other a thin client. The PC doesn't have this problem.
With terminal services, you must have a copy of the front-end for each user. I usually put a folder on the machine with the front-end in it, and when the users logs in, (s)he is directed to that folder and not permitted to go anywhere else. I have never had a problem with multiple users some with local LAN front-ends, and others on a terminal server (and still others with an asp front end) The web server and database were on the same server, and the terminal server clients had their own server. I have also had multiple terminal server clients on the same server as the back end without any problems.
isn't an Access issue per se....there is nothing in Access which knows that one is using terminal services, so there is no setting or anything that one could change.
whether terminal services or not terminal services; one should split an Access db and establish a front end.mdb (FE) for each user. in a non terminal services environment you put the FE on the PC of each user. in a terminal services environment you put that FE in each users virtual space - the exact instructions depend on the version and maker of your terminal services...and so you will want their assist.....
"Kelly" wrote: > Hi, I'm running an Access database that's been running for 2 years without > problems. I have the backend on a Sequel2000 Server and never had any > problems with it. I now swapped out the computer with a thin client running > Terminal Services. I was using Access 2000 and the problem is that the thin > client access application keeps locking up. The mouse click seems to stop > working for the access application. Is there something special I must do to > use this database in a terminals service session? > I ended up making it an MDE thinking this would help, but it didn't seem to > change anything. I only have (2) users using the database, (1) being a PC and > the other a thin client. The PC doesn't have this problem.
> "Kelly" <Ke...@discussions.microsoft.com> wrote in message > news:AFE54F95-CEB4-4C59-9397-862D986B8077@microsoft.com... >> Hi, I'm running an Access database that's been running for 2 years >> without >> problems. I have the backend on a Sequel2000 Server and never had any >> problems with it. I now swapped out the computer with a thin client >> running >> Terminal Services. I was using Access 2000 and the problem is that the >> thin >> client access application keeps locking up. The mouse click seems to stop >> working for the access application. Is there something special I must do >> to >> use this database in a terminals service session? >> I ended up making it an MDE thinking this would help, but it didn't seem >> to >> change anything. I only have (2) users using the database, (1) being a PC >> and >> the other a thin client. The PC doesn't have this problem.
> With terminal services, you must have a copy of the front-end for each > user. I usually put a folder on the machine with the front-end in it, and > when the users logs in, (s)he is directed to that folder and not permitted > to go anywhere else. I have never had a problem with multiple users some > with local LAN front-ends, and others on a terminal server (and still > others with an asp front end) The web server and database were on the same > server, and the terminal server clients had their own server. I have also > had multiple terminal server clients on the same server as the back end > without any problems.
> "Kelly" <Ke...@discussions.microsoft.com> wrote in message > news:AFE54F95-CEB4-4C59-9397-862D986B8077@microsoft.com... >> Hi, I'm running an Access database that's been running for 2 years >> without >> problems. I have the backend on a Sequel2000 Server and never had any >> problems with it. I now swapped out the computer with a thin client >> running >> Terminal Services. I was using Access 2000 and the problem is that the >> thin >> client access application keeps locking up. The mouse click seems to stop >> working for the access application. Is there something special I must do >> to >> use this database in a terminals service session? >> I ended up making it an MDE thinking this would help, but it didn't seem >> to >> change anything. I only have (2) users using the database, (1) being a PC >> and >> the other a thin client. The PC doesn't have this problem.
> With terminal services, you must have a copy of the front-end for each > user. I usually put a folder on the machine with the front-end in it, and > when the users logs in, (s)he is directed to that folder and not permitted > to go anywhere else. I have never had a problem with multiple users some > with local LAN front-ends, and others on a terminal server (and still > others with an asp front end) The web server and database were on the same > server, and the terminal server clients had their own server. I have also > had multiple terminal server clients on the same server as the back end > without any problems.
That's good. I do beleive I may have found the resolution to the problem. What I've found is that when the users are calling up drawings from out local intranet, Adobe Acrobat Reader would open up to display the drawing. They would then select the Print icon to print the drawing and the lockup would occur quite often. Yesterday, in the preferences of the reader, I modified the connection which was set to dialup connection at 56kb and changed it to be a LAN connection which it is. I checked the event view on the Terminal Server this morning and I don't see any events from last night, which in the past I saw many events. I think this may have been the root cause. I will monitor this for another day and if all goes well, this was it. I will respond back to verify this. Thank you!
"GBA" wrote: > isn't an Access issue per se....there is nothing in Access which knows that > one is using terminal services, so there is no setting or anything that one > could change.
> whether terminal services or not terminal services; one should split an > Access db and establish a front end.mdb (FE) for each user. in a non > terminal services environment you put the FE on the PC of each user. in a > terminal services environment you put that FE in each users virtual space - > the exact instructions depend on the version and maker of your terminal > services...and so you will want their assist.....
> "Kelly" wrote:
> > Hi, I'm running an Access database that's been running for 2 years without > > problems. I have the backend on a Sequel2000 Server and never had any > > problems with it. I now swapped out the computer with a thin client running > > Terminal Services. I was using Access 2000 and the problem is that the thin > > client access application keeps locking up. The mouse click seems to stop > > working for the access application. Is there something special I must do to > > use this database in a terminals service session? > > I ended up making it an MDE thinking this would help, but it didn't seem to > > change anything. I only have (2) users using the database, (1) being a PC and > > the other a thin client. The PC doesn't have this problem.
Arvin - Thank you, I will take your advice and see if there is something else going on with the server. I'm noticing that the problem with Access buttons not working is now godn and the events seem to be relating to the HP printer driver - it looks like anyway. I will report back my findings.
> "Arvin Meyer [MVP]" <arv...@mvps.invalid> 写入消息新闻:uWpLBEIXKHA.1...@TK2MSFTNGP02.phx.gbl... > > "Kelly" <Ke...@discussions.microsoft.com> wrote in message > > news:AFE54F95-CEB4-4C59-9397-862D986B8077@microsoft.com... > >> Hi, I'm running an Access database that's been running for 2 years > >> without > >> problems. I have the backend on a Sequel2000 Server and never had any > >> problems with it. I now swapped out the computer with a thin client > >> running > >> Terminal Services. I was using Access 2000 and the problem is that the > >> thin > >> client access application keeps locking up. The mouse click seems to stop > >> working for the access application. Is there something special I must do > >> to > >> use this database in a terminals service session? > >> I ended up making it an MDE thinking this would help, but it didn't seem > >> to > >> change anything. I only have (2) users using the database, (1) being a PC > >> and > >> the other a thin client. The PC doesn't have this problem.
> > With terminal services, you must have a copy of the front-end for each > > user. I usually put a folder on the machine with the front-end in it, and > > when the users logs in, (s)he is directed to that folder and not permitted > > to go anywhere else. I have never had a problem with multiple users some > > with local LAN front-ends, and others on a terminal server (and still > > others with an asp front end) The web server and database were on the same > > server, and the terminal server clients had their own server. I have also > > had multiple terminal server clients on the same server as the back end > > without any problems.
GBA <G...@discussions.microsoft.com> wrote: >whether terminal services or not terminal services; one should split an >Access db and establish a front end.mdb (FE) for each user. in a non >terminal services environment you put the FE on the PC of each user. in a >terminal services environment you put that FE in each users virtual space - >the exact instructions depend on the version and maker of your terminal >services...and so you will want their assist.....
Depending on how the users home directories and such are configured you could use the free Auto FE Updater utility see http://www.autofeupdater.com to keep each individuals FE up to date.
|
