Adam
Any time you add an Office product library to your project references you're risking what you have now. Change everything to late binding.
I show an example on my Code samples page of my site thatlldoit.com
If you need more help let us know.
Regards,
Bill Mosca, Founder - MS_Access_Professionals
http://www.thatlldoit.com
Microsoft Office Access MVP
https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E
My nothing-to-do-with-Access blog
http://wrmosca.wordpress.com
--- In MS_Access_Professionals@yahoogroups.com, "AdamF" <runuphillracing@...> wrote:
>
> We're transitioning from XP to Win7, and Access2000 (yup) to 2010. For now we're still using 2000, however in both XP & Win7 environments. VB doesn't compile the same in XP & Win 7. I think this mainly has to do with reference libraries. For example, in XP, it requires the MS Office Excel and Outlook 11.0 Object Libraries, while in Win7 it needs 14.0.
>
> Is there a way around this or is it something we just have to put up with until we're all on Win7? The biggest problem seems to be with Outlook, with the SendObject command.
>
> Thanks
> Adam
>
Rabu, 25 Juli 2012
[MS_AccessPros] Re: Access/VB in XP & Win7 environments
__._,_.___
.
__,_._,___
Langganan:
Posting Komentar (Atom)
Tidak ada komentar:
Posting Komentar