I wanted to post the responses that I got from this problem, so that I 
could share them with others who may have the same issues. 

Thank you, Mark! The information that you sent me (below), coupled with 
just discovering that I could click "View" in the menu bar and then 
click "View Controls As Text", has made InterDev debugging make sense!!! 
I just click somewhere in my code in sourceview and then press Ctrl-G and 
then type in the line number and voila, I am at the line with the 
problem!!! I was trying to count the lines of code - a nearly impossible 
task. Thank you from the bottom of my heart!
 ----------------------------------------------------------------------
Message #1 by "Mark" <MMOBERLY@m...> on Mon, 18 Feb 2002 20:35:00 -0600 
Reply to this message (you must be a subscriber to reply)  
 

I'm not sure what the error message relates to in the long run...

> I can find no way to identify line 334 (the problem line) in the code 
generated by Visual InterDev.

...however, after also floundering with the problem of identifying 
specific lines referenced by error messages, I finally discovered 
CTRL+G...then, enter the line number, ENTER...and, the line in question 
will be highlighted...from which point you can begin the next step, i.e., 
solving the real problem...

Mark.