Richard,
The file that does exist is on my laptop is msvcp140.dll not msvcr140.dll. It appears in the FMS Data Manager folder, the windows system32 folder, and many other locations. However I find no other copies in any of the folders in my PATH variable. Even if there were multiple copies somewhere within the folders of the PATH variable it would not be wise to delete them because to do so could adversely effect other applications. What is becoming clear to me is that there are many other applications on this pc that use this runtime library without triggering this error as did FMS Data Manager prior to the update.