Re: Access Runtime on PC without MS Office
- From: Rick in NS <rbutler@xxxxxxxxxxxxxxxx(donotspam)>
- Date: Sun, 8 Oct 2006 19:29:02 -0700
Oh boy!!! I have peppered the application with code to control toolbars
using the CommandBar object which I believe is in the Microsoft Office Object
Library 11.0 which is one of the references in my application but not in the
Access 2003 default. In addition I have an Excel pivot table which relies on
the Office XP Web Componets (OWC10.DLL) to function properly. Removing
either the reference to the WDC10.DLL or to the Office Libary 11.0 kicks out
numerous compile errors.
I don't pretend to understand the concept of 'late binding'. Is there a fix
for this; or am I going to have to rewrite the application removing any
reference in the code to the CommandBar object or to a OWc10.PivotTable?
Would another approach; insisting the target machine have some version of
Office on it resolve the issue?
--
Rick in NS
"Rick Brandt" wrote:
.
"Rick in NS" <rbutler@xxxxxxxxxxxxxxxx(donotspam)> wrote in message
news:863C896D-556E-49E9-B30A-5F1ECBAC1E20@xxxxxxxxxxxxxxxx
I am using Microsoft Office 2003 and Visual Studio 2005 with Access Developer
Extentions to package an application for deployment. My understanding is the
the application should run on another machine using the runtime version
included in the package. However; I am testing the application on a clean
machine which does not have any copy of MS Office on it. The application
runs most routines uneventfully. However; certain forms displays and reports
based on queries fail with "Function is not available in expressions in query
express ....."
I have found references from Douglas Steele, MVP and Ken Snell, MVP that
indicate this has to do with missing references to files with an explanation
on how to check the target machine for these missing reference.
However; the target machine does not have anything on it but the runtime
version of Access and the application front-end is in MDE format. So, it is
not possible to open a code module or the debug window to check the reference
on the target machine.
Any suggestions on how to deal with this thorny issue?
On your PC open a new blank file and then check the references. These are the
default references for an Access app in Access 2003. Then compare that to the
references in the file you are having problems with. Are there any additional
references?
If there are the solution is to remove them. No app that you intend to
distribute to multiple PCs should have anything but the default references in it
or you will have no end to these headaches.
If you need to use external libraries (Outlook , Word, etc.), then use late
binding so that you don't have to set references.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
- Follow-Ups:
- Re: Access Runtime on PC without MS Office
- From: Rick Brandt
- Re: Access Runtime on PC without MS Office
- References:
- Re: Access Runtime on PC without MS Office
- From: Rick Brandt
- Re: Access Runtime on PC without MS Office
- Prev by Date: Re: How do I use Access 2003 with SQL Server Express?
- Next by Date: Re: How do I use Access 2003 with SQL Server Express?
- Previous by thread: Re: Access Runtime on PC without MS Office
- Next by thread: Re: Access Runtime on PC without MS Office
- Index(es):
Relevant Pages
|
Loading
