Excel Changing Object Library on me

[jcg31]

I have an Excel application that creates a task and places it in the users tasks in msOutlook. It was written on a msOffice 2003 machine for users with the same set up, it uses the msOutlook 11.0 Object Library on the Outlook side. As long as it is opened and saved in a 2003 Office environment everything works fine, but if it is opened and saved from Office 2007 or above, it no longer plays well with Outlook 2003 because it seems to adopt the appropriate object library for that version of Office in dealing with Outlook (msOutlook 12.0 Object Library in 2007's case). Is there a way to make certain the code always is looking for msOutlook 11.0 Object Library?

Thanks for any help.

Jim

 

[GTO]

Alas, you have discovered what having an older version at home (or wherever) is like.

Anyways, the easy answer (okay, a bit of editing is involved) is to change to late binding. That is, change stuff from like As Outlook.Application to As Object. In Outlook's case, I don't think the performance hit would likely be noticable.

Hope that helps,

Mark

 

[jcg31]

A bit.

while in msOffice 2003, I made the change to late binding in the three locations in the code where the library was referenced. I ran it - - it ran fine, populating the task as expected. I saved the file to the hard drive and then emailed it to me (so I could open on another machine). I then opened and ran the same file on a msOffice 2007 machine, it ran fine, populating the tasks to Outlook as designed. I then saved it on the hard drive of the 2007 machine and sent it back to the 2003 machine. When I tried to open it I received the can't find project or library error again.

Jim

 

[GTO]

While in the older version, did you remove the reference to the library before your last save?

If that's not it, I would carefully look at every decaration to make sure I didn't forget one.

If its still goofy after making sure the library is non referenced and you've gandered all the code, post it.