>>It is my log. I look at the very last records (of this morning US time) where the date and time stamp are today's.
>>Another thing I noticed is that the error was triggered by something in .MPX file. Although the customer was telling me that he was hitting the error when click on a combo box in one of the reports (Group By). And it would crash before any items in the combo would appear.
>
>The trace may well be incomplete. Yes, something in an .mpx because you went through the menu to the point where it happened, but how many more steps? It's an error condition, so you can't fully trust that the stack info logged is perfect.

Yes, you are correct that everything starts in the menu and then hits an error somewhere down the line. And you are also correct that one cannot trust the stack created by C0000006 error. I think most likely this error was cause by the memory corruption on the PC. Which reboot has fixed.

And I may know (or guess) why the log refers to the application executable in the old folder instead of the current folder.

The run-time DLLs on this user's computer were installed way back, when the application resided in the old folder. So, I am guessing, somewhere in his computer registry it refers to as the old folder/location. Hence, when C0000006 hit it took the value from the registry and used it. I am just guessing of course.