I have been using DNS med v10.1 for ~2yrs. Over the years I have created and successfully used hundreds of macros (saved in MyCmds). In a past post I reported that for some reason the MyCmds.dat file becomes corrupt in such a way that Dragon will recognize old commands but will not recognize any new commands that I create. Thanks to this forum the only successful "fix" was to delete MyCommands, reboot, then import an older saved MyCmds.dat file that I know was not corrupt at the time it was saved.

I recently upgraded to Dragon Medical Practice 11 and Knowbrainer 2011 and the problem continues. Every MyCmds.dat file that I import will become corrupt within a few days. The odd thing is that when the file becomes corrupt Dragon will still recognize old commands but will not recognize any new commands that I create.

HELP!!!

Any advice will be greatly appreciated as I am constantly creating ne commands on a daily basis.

I would suggest exporting your custom commands manually from the file while it is still intact (not corrupted), and re-importing them into a new MyCmds.dat file. In order to do this, use the export/import utility in the commands browser.

Rüdiger

Well, it's past the point where we can make any changes in the code, but we can still make changes to the Easter Egg!

Thanks for the advise. As you can see from my post, I've already tried that approach, however, the imported file eventually becomes corrupt as well.

Thanks!

My understanding is that your approach is to delete the file MyCmds.dat when it becomes corrupted, and copy over a previous version, which again will become corrupted. My suggestion then was to try a different approach.

Rüdiger

Well, it's past the point where we can make any changes in the code, but we can still make changes to the Easter Egg!

Hi Rudger,

 I think we are on the same page but something is getting lost in translation, unless, there is a difference between deleting MyCmds from the Command Browser, from Exporting them. My process was as follows: the "healthy" MyCmds.dat files were originally "Exported", when I learned that my custom made commands became corrupt I would then delete "corrupt" MyCmds from the Command Browser, then an old "healthy" MyCmds.dat file was imported via the Command Browser. Soon enough it becomes corrupt again.

Unless I am misunderstanding your suggestion I am assuming that I did exactly what you suggested?

Obviously, there is a slight misunderstanding going on. My suggestion is to not export/import the entire file because that turns out as to become corrupted sooner or later as it seems, but to export/import your individual custom commands by creating a dedicated DAT or XML file.

To do this, open the command browser with a MyCmds.dat containing your custom commands loaded, while it is still intact, and choose "Manage", which will give you a screen like this:

Just make sure that you place a checkmark in every box showing up, then choose "Export", which will take you to a file save dialog next where you have to enter a name for the export file and a location to save to. Then, delete MyCmds.dat from the profile, but don't re-import MyCmds.dat the next time, but close the profile and relaunch it. This will make it start with a new MyCmds.dat this time (in manufacturer state so to speak, therefore likely not going to get corrupted any longer). Now, in order to add your custom commands from the previous version, re-import them using your own export file as described above. You may get prompted that the commands need to be validated, just confirm, and you will be prompted whether to overwrite existing commands, just say no.

I hope this is a little clearer now, and you can go ahead like this.

Rüdiger

Well, it's past the point where we can make any changes in the code, but we can still make changes to the Easter Egg!

I concur with this technique.  But one possibly-important detail is that the export to XML is slightly different than the export to DAT format.   Given the command corruption, I suggest the export to XML.   Over the years I've had two instances where the export to XML then import from XML has worked while the export/import from DAT does not solve the corruption issue.

If you have "validation" errors in the import from XML process, pay attention to them as it may suggest commands that have problems that need to be addressed.

Larry Allen
Softnet Systems, Inc.
http://www.pcspeak.com

Click KB 2012 REV D to Download a 30 Day Evaluation of KnowBrainer 2012 

Hi Lunis,

I do have close to a thousand commands so I am trying to avoid starting from scratch.

Do you think uninstalling DNS Medical 10.1 and Dragon Medical Practice 11, then reinstalling from scratch, then importing a healthy MyCmds.dat file would be a prudent, permanent solution?

Click KB 2012 REV D to Download a 30 Day Evaluation of KnowBrainer 2012