Tracking and pinpointing errors in a VB code macro

[Lt. Krul]

When I run a macro, I get to a point in the running where I get an error "subscript out of range". How can I track/trace the code when it's running in order to pinpoint when/where the error occurs and what the out of range values are. I'm sure there's an easy way. I've tried the "run to curser" method but that won't pinpoint the spot in the code that causes the error.

Thanks a million for your responses...

[Mark O'Brien]

In the VBE, right click on a toolbar and select "Debug" from the list. One of the buttons on the "Debug" toolbar allows you to go through you code one line per click of the button. I think there's an icon of a white hand to the right of it.

Also, you want to hit the button that has the tooltip text "Locals Window" (on Debug toolbar) this let's you see the values of all of your variables while code is running.

(This may be slightly wrong because this is all off the top of my head, but hopefully someone will correct me)

HTH

_________________
[b] Mark O'Brien

[ This Message was edited by: Mark O'Brien on 2002-05-14 19:55 ]

[Tom Schreiner]

Also the F8 key will step through the code.
If you will be writing procedures on a regular basis, I can not empasis this enough!
Take the neccesary steps to learn how to debug!
This may be a bit long-winded for the board, but here is an overview of some of the debugging tools available...

Tom

Edited too long reply for us poor guys with 28K connections and that Mark guy.

For information about debugging, please see the following links:

http://www.j-walk.com/ss/excel/tips/tip11.htm

http://msdn.microsoft.com/library/en...ggingtools.asp

http://advisor.com/Academy.nsf/vSemID/IMD1019

There are many others as well...

[ This Message was edited by: TsTom on 2002-05-15 15:45 ]

[Lt. Krul]

Hey guys, this is really great stuff...I suppose if I fished through help long enough I'd find it, but it's always nice when you experts can provide "instant" help.

I appreciate it and will let you know how it all turns out.

[stevebausch]

I will test the indice:

If indice< LBound(array) or indice>UBound(array) Then

Msgbox "problem with array, indice set to " & indice
End if

Set break point on the endif line, and wait to see what you catch.

[Lt. Krul]

Hello again...
I am suspecting that if I received a "subscript out of range" error, that I have a variable or expression (something) that at somepoint is being forced to handle a value outside it's limits...
Listed below are my opening statements.
Do any of these need to be dimensioned within a range or with upper or lower limit?:

Sub displayfiles()
'CREATED BY JAMES R JEWETT APRIL 2002
'LAST EDITED May 13, 2002 - added multiple worksheet checker and sub code collection code.

Dim fso As Scripting.FileSystemObject
Dim fld As Scripting.Folder
Dim fil As Scripting.File
Dim shtcnt As Integer
Dim x As Integer
Dim y As Integer

x = 2

Dim targetDate As Date

[Vas]

"Subscript out of range" means that you're trying to change or view elements in an array, but in a wrong place.

Dim a(1 to 10) As Integer

a(1) =5 'will work
a(3) = a(1) 'will work
a(11) =5 ' won't work

Try to look for arrays. The problems probably there.

/Niklas Jansson

[Mark O'Brien]

TsTom,

Posting the link to the MSKB would have been too easy, huh?

EDIT:: I'm the "Mark guy" and TsTom changed his post.
_________________
[b] Mark O'Brien

[ This Message was edited by: Mark O'Brien on 2002-05-16 09:27 ]

[Tom Schreiner]

I stand corrected.

[Tom Schreiner]

Hi Lt.
Could you post the code and tell which line is raising the error?
Tom