Hi,
Not sure if this is the right place, but here goes.
I now have MS 2010, however the company DB is 2003 and uses CDO 1.2.1 , up until MSO 2007 everything was fine!
Now Outlook 2010 won't allow you to install CDO 1.2.1 , so I can't even use the main company DB let alone continue to develop it.
What do I do?
MS knowledge base goes on about re-developing the email functionality using MAPI etc...
But if i do that, won't users with MSO2003 then not be able to use it?
How on earth do I make our access database compatible with user on 2003 and 2010?
Also when I open the DB in 2010 it changes all the office references from 11 to 14? How do I stop this, how can I develop an Access DB in 2010 with references to office components in 2003.
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Google Rank Extractor -> Perl beta with FusionCharts
Not sure if this is the right place, but here goes.
I now have MS 2010, however the company DB is 2003 and uses CDO 1.2.1 , up until MSO 2007 everything was fine!
Now Outlook 2010 won't allow you to install CDO 1.2.1 , so I can't even use the main company DB let alone continue to develop it.
What do I do?
MS knowledge base goes on about re-developing the email functionality using MAPI etc...
But if i do that, won't users with MSO2003 then not be able to use it?
How on earth do I make our access database compatible with user on 2003 and 2010?
Also when I open the DB in 2010 it changes all the office references from 11 to 14? How do I stop this, how can I develop an Access DB in 2010 with references to office components in 2003.
"In complete darkness we are all the same, only our knowledge and wisdom separates us, don't let your eyes deceive you."
"If a shortcut was meant to be easy, it wouldn't be a shortcut, it would be the way!"
Google Rank Extractor -> Perl beta with FusionCharts