Access 2002 - 2003

[Guest]

I'm desperate for an answer.

I've developed a database using Access 2003 in an Access 2002-2003 file
format. The problem is that I have users who only use Office 2002...that's
why I use an Access 2002-2003 file format so both Access 2002 and Access 2003
users can run the .mdb. Access 2003 users run the database fine, but Access
2002 users cannot. This is what I've been able to find out so far.

I use Access 2003 to develop the database. In the References section of
VBA, there is a reference to "Microsoft Outlook 11 Object Library" at
c:\Program Files\Microsoft Office\Office 11\msoutl.olb.

When I copy the .mdb over to an Access 2002 machine and check the
references, the Access 2002 VBA references "Microsoft Outlook 10 Object
Library" at c:\Program Files\Microsoft Office\Office 10\msoutl.olb.

My question is, how do I setup the database in Access 2003 so that it can
successfully run in Access 2002?

thanks in advance for any help!

 

[Allen Browne]

Use late binding:
http://support.microsoft.com/kb/260410/en-us

 

[Guest]

Allen...thank you for responding, however the link below is for Microsoft
Office 2000 automation help file, is it possible there is a typo in the url?

 

[John Vinson]

Allen...thank you for responding, however the link below is for Microsoft
Office 2000 automation help file, is it possible there is a typo in the url?

It'll still work.

John W. Vinson[MVP]

 

[Arvin Meyer [MVP]]

The default format for both versions is the Access 2000 file format. You
only need to use the 2002/2003 format if you are making an MDE file. The
article below on late binding works with any version.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Tony Toews]

When I copy the .mdb over to an Access 2002 machine and check the
references, the Access 2002 VBA references "Microsoft Outlook 10 Object
Library" at c:\Program Files\Microsoft Office\Office 10\msoutl.olb.

To add to Allen's posting.

Late binding means you can safely remove the reference and only have
an error when the app executes lines of code in question. Rather than
erroring out while starting up the app and not allowing the users in
the app at all. Or when hitting a mid, left or trim function call.

You'll want to install the reference if you are programming or
debugging and want to use the object intellisense while in the VBA
editor. Then,. once your app is running smoothly, remove the
reference and setup the late binding statements.

Sample code:
' Declare an object variable to hold the object
' reference. Dim as Object causes late binding.
Dim objWordDoc As Object
Set objWordDoc = CreateObject(" Word.Document")

For more information including additional text and some detailed links
see the "Late Binding in Microsoft Access" page at
http://www.granite.ab.ca/access/latebinding.htm

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