Program Crashes Under Load

[dflak]

My apologies for an “amorphous” question. I developed an application for my customer that works just fine. In about one out of 30 runs, it crashes without an error message.

The part of the program that is malfunctioning is that which reads a directory of files. It opens them, reads rows of data, puts them into a table and closes the file.

The “crash” only seems to happen when the system is under load. The nature of the crash is that it opens the file and stalls. It is usually part way through the files in the directory when it does this.

I have Application.Screenupdate = FLASE at this point. I do not see the other files opening and closing.

The frustrating part is that I can’t duplicate the problem.

Short of telling the customer to reduce the load on their computer is there anything else I can do?

I had a similar problem a couple of years ago when copying and pasting pictures. However, in that case, the program produced and error that I trapped and re-ran the subroutine recursively until the “all clear: and the copy was successful.

I am wondering if there is something I can trap here

The program has too much proprietary data in it to sanitize. The best I can do is post the code.

Please Login or Register  to view this content.

[MarvinP]

Hi dflak,

I'd try to throw in some DoEvents in the code. This allows the code to wait for the OS to perform other tasks and come back to the code.

[mjr veverka]

As above and maybe something like a code below ... something in this direction:

Please Login or Register  to view this content.

[Sintek]

Hey there dflak...

puts them into a table and closes the file.

I'm guessing your issue is caused by the above...
Try changing your Tables to Ranges or change your code to Listobject specific referencing...
Also, no need for all those loops...
Also, perhaps ideal to process all the data in memory and then write back to sheet...
Can only ascertain with a sample though...

[dflak]

Thanks for all the responses. The DoEvents will be the easiest to implement.

I get the comments on the loops. They are afterthoughts. I am still discovering new ways that the data can be dirty and has to be cleaned up. I may pull that code out into a separate module and clean it up. These loops occur after the file data are imported.

The requirements are still a work in progress.

As for using ranges instead of tables. The data will have to be put into a table eventually. I suppose I can import it into a range and when it's all done, copy the range into a table. That might actually be quicker since the table has an number of columns that do calculations. Might as well do that all at once instead of incrementally. Don't import and try to think at the same time.

Food for thought.