Access application on Terminal Server

Hi,

We have several Access applications running on a client's terminal server.

Windows Server 2008 R2 Enterprise
Access 2010

Every couple of weeks, Access seems to act up and the IT team has to do a re-install to correct the issues. When we go to delete objects (forms/reports), we confirm the delete, but they are still there. We have close and open the application again to see that they have been removed.  Also we can not always navigate between views (ie form view / design view). The functionality is greyed out in the ribbon.

Has anyone run into these issues before?

A re-install does solve the problem, but there seems to be a bigger issue since we have to keep re-installing the program every couple of weeks.

Thanks for your time :)
S_HamelAsked:
Who is Participating?
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Connect With a Mentor Infotrakker SoftwareCommented:
Access has to be re-installed/repaired
That's a problem with the installation of Access/Office on the TS, or a problem with the installation of the Operating System. Access should not have to be repaired each time.

Is 2010 the ONLY version of Access on the TS box? Multiple versions of Access can cause all sorts of issues, especially if they are run concurrently.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
When you say "reinstall the program", do you mean you have to reinstall Access, or you have to "reinstall" your Access database?

If you've got to reinstall Access, then I'd suggest there is something wrong with the Terminal Server. Access/Office should not require regular reinstalls unless something else is happening (i.e. power surges, power cycles, etc) - and your server logs should tell you this.

If you mean your Access database has to be "reinstalled", then that could be caused by a number of things. For example, is the database split into a Backend (the tables only) and a Frontend (everything else), and does each user have their own copy of the Frontend?

Is the database hosted directly on the terminal server machine, or on a network share? It really should be hosted directly on the machine.

Sometimes maintenance needs to be done to your database - for example, create a new, blank database and import everything into that database. This tends to remove corruption, although you sometimes must take additional steps.
0
 
S_HamelAuthor Commented:
Thank you for the reply.

Access has to be re-installed/repaired. Not the actual Access database.

I'm not positive if it's installed on the machine or share. I will have to ask the IT department.
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
S_HamelAuthor Commented:
I though we had the issue under control after a full re-install of Office, but it has happened again.

The only other reference online I can find is here: (scroll down to the posts starting Jan 7, 2014)

http://social.msdn.microsoft.com/Forums/en-US/1701369c-02b4-4f43-abe7-03b099b4d517/access-2010-form-fields-not-calculating-until-clicked?forum=accessdev

I have had this happen in our dev environment on our own server, plus client's servers.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
As was indicated to you in the link, there is very likely something wrong with the combination (OS + Office combo, that is). I don't think there is much we could help with on that.
0
 
S_HamelAuthor Commented:
Thanks Scott. There is no definite solution right now, but your response pointed me in the right direction. I will post any updates as I come across them for future reference.
0
All Courses

From novice to tech pro — start learning today.