Office version mix up!!!

[PiedPiper70]

Until yesterday - I maintain a client database created in Office 2003 Pro but the client machines have Office 2003 standard but with Access 2010 runtime. This worked fine.

Yesterday I took the plunge and upgraded my machine to Office 2010 Pro. I gave my client a new version of the front end last night but unfortunately it never occurred to me that the references to Word, Excel and Outlook would cause problems as the versions do not match. My application makes use of all 3 Office progs on a regular basis. They all got errors this morning so I had to revert - a little embarrasing to say the least.

How on earth do I get round this? Getting the client to upgrade 100 machines is not an option. I suppose I could downgrade my own Word, Excel and Outlook to 2003 and keep Access 2010, but I'd rather not.

So if anyone has any suggestions I'd love to hear them

Thanks in advance
Dave

 

[GinaWhipp]

The only thing that comes to mind is use Late Binding. Take a look at...

http://www.granite.ab.ca/access/latebinding.htm

For examples…
http://word.mvps.org/FAQs/InterDev/EarlyvsLateBinding.htm

 

[PiedPiper70]

Thanks Gina

I'm checking out late binding but I'm encountering a few issues. My program probably contains 50 or so references to early binding and I'm just working my way through.

In the meantime if anyone can suggest another way I'd be only too happy to listen.

My current favourite strategy is probably to revert to Office Pro 2003 which seems a retrograde step but it will work

 

[GinaWhipp]

With so much early binding I would suggest reverting back while you *fix* your database. This keeps everyone happy and gives you time to fix and test!