Microsoft Dynamics GP Developing for Dynamics GP
A blog dedicated to the Microsoft Dynamics GP Developer & Consultant community
 
Welcome to MSDN Blogs Sign in | Join | Help

Developing for Dynamics GP

by David Musgrave (Australia) and the Microsoft Dynamics GP Developer Support Team (USA)

News

  • Please use the Blog Feedback? - Contact Us link at the top of the page to email questions relating to the blog itself.

    If you wish to ask a technical question, please use the links below to ask on the Newsgroups. If you ask on the Newsgroups, others in the community can respond and the answers are available for everyone in the future.

    Please do not use comments on pages and posts to ask questions unrelated to the topic on that page or post.



    Dates of Interest:

    11-Jul-2008: Blog Created by David Musgrave.
    10-Oct-2008: First Post by Scott Stephenson.
    04-Nov-2008: First Post by Dave Dusek.
    11-Nov-2008: First Post by Beth Gardner.
    28-Nov-2008: First Post by Chris Roehrich.
    30-Dec-2008: First Post by Patrick Roth.
    24-Feb-2009: First Post by Greg Willson.
    22-Apr-2009: First Post by David Clauson.
    04-May-2009: First Post by Ryan Wigestrand.
    19-Jun-2009: First Post by Dawn Langlie.
    03-Jul-2009: First Post by Emily Halvorson.
    23-Sep-2009: Created Twitter account with blog feed.



    WorldMaps Statistics since
    24-Feb-2009:




    Click for WorldMaps Stumbler



    Translator Tool:




    Social Networking

    Follow David Musgrave and the blog on:

    David Musgrave on Twitter

    David Musgrave on LinkedIn


    Disclaimer

    This blog is provided "AS IS" with no warranties, and confers no rights.

    The links in this blog may lead to third-party Web sites. Microsoft provides third-party resources to help you find customer service and/or technical support resources. Information at these sites may change without notice. Microsoft is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.

Contents

Favourite Posts

Blog Links

Newsgroups Links

Resources Links

Dex - How to Fix the File Association for the .DIC extension

David MeegoIn the Dex - Identifying the build number of a Development Dictionary post, we covered using the Windows Explorer to get the dictionary version from the file properties.  This only works if the .DIC extension is correctly associated with Dexterity as a Dexterity Dictionary.

On my system, I find that every time Windows Update installs updates to Microsoft Office, the .DIC extension is changed to be associated with Notepad as a Text Document.

Below are the steps to change the association back using the Registry Editor.

  1. Click Start >> Run..., type "RegEdit" and press Enter or if Run is not enabled, Click Start and in the Search field, type "RegEdit" and press Enter.
     
  2. Locate the Computer\HKEY_CLASSES_ROOT\.dic node.
     
  3. Change the string value for the Default registry key from txtfile to DIC_auto_file.
     
  4. Close the Registry Editor window.

DISCLAIMER:  The Registry Editor should be used carefully and only if you are comfortable making registry changes.  Use of the Registry Editor is not supported.

Attached to the bottom of this post is a zipped .reg file which can be double clicked on to make the same change to the registry.

Hope this helps. 

David

Posted: Wednesday, July 01, 2009 9:00 AM by David Musgrave
Filed under:

Attachment(s): Dictionary Association.zip

Comments

No Comments

Leave a Comment

(required) 

(required) 

(optional)

(required) 

  
Enter Code Here: Required

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Page view tracker