05-01-2013 04:14 PM
Yeah that's why I don't understand it, no matter what there should be some data there
That's one of my theories, that somehow something is wrong with the OS when accessing the HD or during buffering. On of the pains is that to do any kind of re-installing or hardware management I need to do it through IT since we (I mean we Engineers) have no administrator rights .
The biggest problem I'm having right now is trying to explain to management and other engineers that I really don't fully understand why this is happening and since it happens very randomly is hard to replicate and hence very hard to fix and prove that it's been fixed.
Thanks for the input and ideas, I will try some of them.
05-01-2013 04:14 PM - edited 05-01-2013 04:27 PM
OK, looking at the code....
Nothing wrong with the file write. Try to not convert EOL, see if it makes a difference.
Since you say it is a rare event and only occurs in the executable, check if the runtime engine is current (e.g. SP1 vs non-SP1, etc). Does it occur on all machines with the executable or only on one particular PC?
Why do you need to write to the file in the innermost loop. Wouldn't it make more sense to write multiple lines after the FOR loop instead?
Do you write to a local drive or is the file at a network location?
btw, here's how it would look like using "array to spreadsheet string".
05-01-2013 04:25 PM - edited 05-01-2013 04:26 PM
Good points altenbach.
I did think about disabling the convert EOL and see if it makes a difference, I will do it and try it.
I do have SP1 installed.
It does write to both a local HD and into a network drive (not at the same time, we used to write to local and now it's to a network drive) and the problem presents itself on both.
Thanks for the tips. I will try these changes and wait and see.
05-01-2013 04:30 PM
JMotaB wrote:I do have SP1 installed.
Are all the runtime engines on the target machines also SP1?
I edited the message above to ask if it only occurs with certain PCs or with all.
05-01-2013 04:59 PM
This software only runs in one machine. I don't have the model right now but I can find out. What I do know is:
- Windows 7 Professional
- SP1
- Intel Core Duo 2.93 GHz
- 32-bit