| suv2@mail.ru 2005-09-20, 7:55 am |
| > Do you mean to say your going to run this utility 200 times in a tight loop??
As I have already told, my programm need to run the external utility.
Many many a times. Not in a loop like "for.....next". The user
initiates "swpruncmd()" by the own actions. The programm fails after NN
hours continuous job.
> If not the test is pointless - your chasing shadows
swpruncmd("dir *.txt") - is pointless, but the test shows a PROBLEM.
> If your test fails after 1 or 2 iterations then I'd say you might have found a problem,
The programm fails after NN hours continuous job. This is the problem.
> Well why not change the model your using - write a windows app that monitors
> some directory/settings and runs the utility as another process.
> No need for swpruncmd() at all then.
I perfectly see this way. Nevertheless i wish to try to make, that
swpruncmd worked.
|