>>>>One of the reasons I am not "moving" the application to the local drive is as follows:
>>>>
>>>>I am still not 100% that the problem is not in my code. The error log files is written to the network drive/share. So, clearly the application is connected to the network drive/share. And the error - in many cases says that the "application cannot read either .FXP file or .VCT file or .DCX file" This is why I am trying to check if the code always "points" to the correct FXP/VCT/DCX file.
>>>>
>>>
>>>If you're dealing with wireless connections, AIUI, you can have momentary drops. If your code happens to execute just as there's a drop, ...
>>>
>>>Tamar
>>
>>It could be. But as my other thread - on Start method - indicates, there must be a problem in my code. At least, I think so now.
>
>Really, you should be loading your application files to the app folder.
>
>The fact that it still logs can easily be explained, as an intermittend network drop breaks the connection to the EXE, but your error routine then still could log the file if it opens the error log within the error handling.
>
>I've seen too much of this in the past. I'd say I'm 99% sure your problems can be solved in copying the app locally in the appdata folder.
>
>Walter,

Thank you for your input.

You are right IF the problem is NOT in my code. But if the problem is in my code, then even if I move the application to the local folder, I will continue seeing this problem. This is why I am checking all places in my code (see thread on Start method) to see if the CLEAR EVENTS that fires before it should fire, causes the problem.

I found some places in the code where this may happen. And I will add some TEST code to log these events. Then I will be able to compare the error log with these events log and see if/what I need to change in my code.