<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Use OMPM to Prepare for Migration to Access 2007</title><link>http://blogs.msdn.com/access/archive/2009/06/09/use-ompm-to-prepare-for-migration-to-access-2007.aspx</link><description>Today’s guest writer is Shawn Sullivan from the Office Shared team. I have asked him to talk about the work he has done to help organizations move to newer versions of Office. In March, we made a post about Office Migration Planning Manager (OMPM), which</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator></channel></rss>