Will multi thread solve this problem or is there a better way?

[azdjedi]

Hey,



Thanks for reading.

Here's the situation. I have an Import database that Windows Scheduler runs every 15 minutes on a server that isn't monitored (excpet during 9-5 hours). It does multiple things based on internal settings that aren't relevant here. The problem that happens is sometimes Access crashes, or Excel crashes, or Outlook crashes. Because of this I've set up a VBS task that runs at 4am every day--it simply force closes everything and restarts them. Great.

The problem I'm still having is sometimes Office will crash intraday; I'd like for my VBS script to run every 15 minutes...to start fresh each time. The issue with that is if the "every 15 minutes" script is still importing stuff then the VBS script will kill it before it's done. I could set it to run every 30 minutes, but again, timing crossover is possible.

I was thinking I could have the Import database write to a file every 1 minute so the VBS script could check if it's being updated. MS Access has the form timer, but it doesn't run concurrently with the real vba code.

Any suggestions?

Thanks.

[orange]

Why are the various systems crashing? How come Access, Excel and Outlook are involved? Can you show the logic of what you are doing in broad terms (the 30,000 foot view) to give readers some idea of context?