>>>>>Has anyone tried their app under Windows 10? A few of my clients are thinking about moving
>>>>>up to 10 and I am trying to anticipate any problems. If you have run under Windows 10, did you
>>>>>have any problems?
>>>>
>>>>I have experienced two so far:
>>>>
>>>>Thread#1628337 (esoteric but reproducible)
>>>>
>>>>Another issue I'm debugging at the moment is Word automation calls that work fine on Win7 but fail on Win10. When I figure it out I'll post details.
>>>
>>>Can you give samples of Word automation calls which doesn't work on Win10?
>>
>>At this point all I have is an app that is 100% reliable on Win7, and 100% C5's on Windows 10. The C5's are happening amongst a series of Word automation calls. I'm working on debugging it.
>
>Continuos coverage log file destroyed by C5 ? Logging with ascending file names might help identify critical sector - if it is a single one ;-))

I'm pretty sure I know where it's happening. In cases like this I usually use a "soft seek" technique (for want of a better term). If I know roughly where the problem happens I insert STRTOFILE( ) calls at the beginning, end and at likely places in between, which create a log file with entries something like

Step 1 reached
Step 2 reached
...
Step n reached

Usually I find something like Step 2 is reached but Step 3 isn't. Then I salt the instructions between them with more calls. Iterating through a "pseudo-binary" approach like that you can fairly quickly zero in on the call causing the failure (as long as it's consistently reproducible).