Procedures stop with no indication of problem
 

I have a macro that opens workbooks on a server on the West Coast (I'm on the
East) and extracts data from multiple files in multiple folders.
Intermittently, it will just stop somewhere in the middle with no obvious
cause of the problem. I have periodic "On Error Resume Next", but I've
followed it with "On Error goto 0" in every case.

I *think* my problem is somehow related to network connectivity, but I don't
know that for sure. Does anyone have a suggestion of something for me to
look for so that I know what's happening and how to ensure it doesn't happen?

Thanks,
Barb Reinhardt

Procedures stop with no indication of problem
 

You can put

Application.StatusBar = "Step 1, File 1"

in several places to see where it hangs.

This appears at the bottom left of the screen.

Procedures stop with no indication of problem
 

I have that in place already and it hangs at different times. Any other
suggestions?

Thanks
Barb Reinhardt

"David Sisson" wrote:

You can put

Application.StatusBar = "Step 1, File 1"

in several places to see where it hangs.

This appears at the bottom left of the screen.

Procedures stop with no indication of problem
 

Try peppering your code with:

Debug.print "some unique identifier here"

(lots of them)

Then you may be able to see where things break.

=====
As an aside, I used to have a file that would open other files on a remote
network and it didn't stop--but it took forever.

I added a step to copy the files to a local temporary folder and ran against
those copies and the speed increase was noticeable.

Barb Reinhardt wrote:

I have that in place already and it hangs at different times. Any other
suggestions?

Thanks
Barb Reinhardt

"David Sisson" wrote:

You can put

Application.StatusBar = "Step 1, File 1"

in several places to see where it hangs.

This appears at the bottom left of the screen.



--

Dave Peterson

Procedures stop with no indication of problem
 

I could do that, but I need to be able to know the original URL for these
files. The strange thing is sometimes it runs through with no problems and
sometimes it just stops. Yesterday, we were having network issues and it
stopped multiple times. Is there some way to "test" for that?

Thanks,
Barb

"Dave Peterson" wrote:

Try peppering your code with:

Debug.print "some unique identifier here"

(lots of them)

Then you may be able to see where things break.

=====
As an aside, I used to have a file that would open other files on a remote
network and it didn't stop--but it took forever.

I added a step to copy the files to a local temporary folder and ran against
those copies and the speed increase was noticeable.

Barb Reinhardt wrote:

I have that in place already and it hangs at different times. Any other
suggestions?

Thanks
Barb Reinhardt

"David Sisson" wrote:

You can put

Application.StatusBar = "Step 1, File 1"

in several places to see where it hangs.

This appears at the bottom left of the screen.



--

Dave Peterson

Procedures stop with no indication of problem
 

Not in my world--but I'm not smart enough to know for sure.

I'd either google for network problems or maybe ask in a newsgroup dedicated to
networks.

Barb Reinhardt wrote:

I could do that, but I need to be able to know the original URL for these
files. The strange thing is sometimes it runs through with no problems and
sometimes it just stops. Yesterday, we were having network issues and it
stopped multiple times. Is there some way to "test" for that?

Thanks,
Barb

"Dave Peterson" wrote:

Try peppering your code with:

Debug.print "some unique identifier here"

(lots of them)

Then you may be able to see where things break.

=====
As an aside, I used to have a file that would open other files on a remote
network and it didn't stop--but it took forever.

I added a step to copy the files to a local temporary folder and ran against
those copies and the speed increase was noticeable.

Barb Reinhardt wrote:

I have that in place already and it hangs at different times. Any other
suggestions?

Thanks
Barb Reinhardt

"David Sisson" wrote:

You can put

Application.StatusBar = "Step 1, File 1"

in several places to see where it hangs.

This appears at the bottom left of the screen.



--

Dave Peterson


--

Dave Peterson