Errors when running Access through a Terminal Server

  • Thread starter Thread starter ChuckW
  • Start date Start date
C

ChuckW

Hi,

I developed an application in Access 2002 that currently
runs on a file server. We also have a terminal server
with Access 2003. I am trying to get the application to
run on the terminal server but there seems to be a series
of problems. One problems is that I get an error message
when I click to get to the main form. The error message
says "Your database or project contains a missing or
broken reference to the file msoutl.olb version 9.1.
Also, I used the trim expression in some of my SQL. But
when I try to run reports based on these queries, I get
an error that says "Undefined function trim in
expression. Another error I get is "undefined Date
Function" for queries that have dates in them.

I built another application that works fine with no
errors but very little VBA. This application that I am
having problems with has quite a bit of VBA code.

Can anyone help?

Thanks,

Chuck
 
ChuckW said:
Hi,

I developed an application in Access 2002 that currently
runs on a file server. We also have a terminal server
with Access 2003. I am trying to get the application to
run on the terminal server but there seems to be a series
of problems. One problems is that I get an error message
when I click to get to the main form. The error message
says "Your database or project contains a missing or
broken reference to the file msoutl.olb version 9.1.
Also, I used the trim expression in some of my SQL. But
when I try to run reports based on these queries, I get
an error that says "Undefined function trim in
expression. Another error I get is "undefined Date
Function" for queries that have dates in them.

I built another application that works fine with no
errors but very little VBA. This application that I am
having problems with has quite a bit of VBA code.
Click to expand...

Your app has a reference to Outlook libraries in it and those libraries
either don't exist on the Terminal Server or they are in a location where
Access cannot find them.

Either remove the Outlook reference or install Outlook on the Terminal
Server. Even if you are using Outlook functionality I would recommend
switching to late binding so that the hard reference is not required. This
also has the benefit of making your code (for the most part) not care about
the version of Outlook on the PC or where the libraries might be located.
Hard references are much less forgiving.
 
Back
Top