Hi David (Marlin)

I had an old FPW26 app that was ported to VFP5 back in 98. Throughout the entire history of the app running (every day for several years), (on both fpw and vfp5) my users would get that error anywhere between every few hours to every few days. I went crazy trying to trace the origin, including numerous exchanges with Fox/MS tech support. I am not sure on this, because it was a long time ago, but, I believe that it went away after we made some operating system/drivers changes. At the time we were also having intermittent file corruption problems. The file corruption abruptly and completely stopped after we went to the Microsoft Network client from a Novell 32 bit client (which I had pleaded with them (the IT dept) to do for months, because I knew there was a problem with the Novell client). But we also changed several other things at the time, as well - MS patches for VXD files that were supposedly related to corruption some how - plus - I think - some other things. Anyway, at some point after we made these environmental changes pertaining to the file corruption, the menu manager internal consistency problem went away too. If I can, I will try to retrieve my notes on this.

Can you tell me more about your OS and NOS environment?



>Hi David.
>
>>I very frequently get 'Menu Manager Internal Consistency Errors' running SDT 6.0c in VFP 7 sp1.
>>
>>I start SDT by running a VFPSTART.prg at VFP startup, using the following line:
>>

do \stonefield\sdt\SDT.APP with 'install', '_msm_tools'
>>

>>as indicated in the help when this error occurs.
>
>The only time I ever got that error was when running two utilities that both did a SET SYSMENU SAVE, so by calling SDT as you do, it doesn't use that command. Also, it seems to me that VFP 7 fixed that issue.
>
>So, I'm not sure what's causing this. You might want to rebuild SDT.APP with "recompile all files" checked just in case something in the APP file is corrupted.
>
>Doug