Thanks Allen. I've read the file you suggest. Does this mean (e.g. with
Outlook) that as long as I replace all my lines such as:
Dim myOutlook As New Outlook.Application
Dim myEmail As Outlook.MailItem
with:
Dim myOutlook As Object
Dim myEmail As Object
Set myOutlook = CreateObject("Outlook.Application")
Set myEmail = myOutlook.CreateItem(olMailItem)
the rest of the code will work OK? What worries me is that I still need to
tick the reference to Microsoft Outlook 10 Object Library to get the last
line to work (else "olMailItem" isn't recognised) - won't VBA still be
looking for this version of the library when the code is run in the older
version of Access?
Thanks,
Martin
"Allen Browne" wrote:
> If you reference the other Office libraries (such as Excel or Outlook)
> across different versions, use late binding.
>
> For more info, grab the file in this link:
> http://support.microsoft.com/default...b;en-us;260410
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia.
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Martin" <(E-Mail Removed)> wrote in message
> news:14665B61-6F9C-4425-9348-(E-Mail Removed)...
> > I've made some changes to a client's Access 2000 database in Access 2002
> > which purports to continue working in the same 2000 format. However, when
> > the client tries to use the database now, they keep getting VBA reference
> > errors because the modules now expect versions 10 rather than 9 of the
> > Excel,
> > Outlook and Word object libraries. Is there any way around this?
> >
> > Thanks.
>
>
>
Similar Threads
