How to add the DWORD value SQLSecurityCheck in Word/Options registery via Regedit?

Anonymous
2019-08-20T19:33:29+00:00

My MS Access program opens a mail merge Word document to prepare a document or a mail with Access data. To avoid an error explaining that the mail merge document is not foreseen for mail merge, I needed to add via Regedit the DWORD value SQLSecurityCheck in the registery HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Options  

However, with the latest version of Windows and Office, I don't see anymore this registry key. What's the "workaround" solution for this new release?

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes
Answer accepted by question author
  1. Anonymous
    2019-08-27T12:17:38+00:00

    Hi Jack,

    As Doug suggested above, you only need to choose either set the SQLSecurityCheck in the Registry or install the add-in on your computer. As I noticed that you didn't have a clear understanding on how to add SQLSecurityCheck in the Registry, please try to follow the steps below to set up.

    1: Press Window key + R and key in " regedit" in the dialog

    2: Select OK to run Registry Editor

    3: Locate the following  registry key: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Options

    4: Right click on Option folder and create DWORD registry key

    5: Rename the created key as " SQLSecurityCheck"

    6:Double click on SQLSecurityCheck and set value data as 00000000, and click okay to save.

    7: Restart your computer.

    If the issue still exists, please also provide as the screenshot of your Office version. You can go to File > Account > Under Product Information to check it.

    Notes: To protect your information, please remove any private information before you share the screenshots with us. Thank you.

    Best regards,

    Dihao

    3 people found this answer helpful.
    0 comments No comments
Answer accepted by question author
  1. Doug Robbins - MVP - Office Apps and Services 322.1K Reputation points MVP Volunteer Moderator
    2019-09-10T07:43:47+00:00

    If what you are saying that the customer "activated" what was probably a trial version on the new PC, it might be best to remove all traces of the Office installation by downloading the fixit from the following article:

    http://support.microsoft.com/kb/2739501

    saving it to the new computer and then running it.

    Then, after re-starting the computer, reinstall Office by logging into www.office.com/myaccount with the registered email address and click Install Office.

    2 people found this answer helpful.
    0 comments No comments

20 additional answers

Sort by: Most helpful
  1. Suzanne S Barnhill 275K Reputation points MVP Volunteer Moderator
    2019-08-20T20:13:59+00:00
    0 comments No comments
  2. Anonymous
    2019-08-21T06:33:34+00:00

    Thank you, Suzanne but is does not help me. My problem is related to a very new Windows 10 / Office version. In this version the Winword.exe programme is no longer installed in c:\Program files\Microsoft Office. And via Regedit, I don't see the registry key HKEY_CURRENT_USER\Software\Microsoft\Office. This is the problem ...

    0 comments No comments
  3. Doug Robbins - MVP - Office Apps and Services 322.1K Reputation points MVP Volunteer Moderator
    2019-08-21T10:15:30+00:00

    With Office 365, running under Windows 10, the key to which you must add the SQLSecurityCheck is

    Computer\HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Options

    However an alternative is to install the MergeSQLMessageEliminator Add-in that is contained in the MergeSQLMessageEliminator.zip file that you can download from the following folder of my OneDrive

    https://1drv.ms/u/s!AmuIXmFDy-1ahDYSiUNl1pFAvGvI?e=ALV4Ts

    Extract the files from the archive and read the Read Me document to see how to install and make use of the utility.

    0 comments No comments