what could cause inability to "Debug..step into" code?

[bbasberg]

Hello,

I am a neophyte with Visual Basic but have been trying to hurry and get up to speed. I used to be able to "step into" code using Debug..step into but for the last couple of days I am unable to. Regardless of where in the code I place my cursor, I hear a microsoft error "thunk" and step into doesn't work. I am using VBA in Access if that matters.

here's one possible clue but it may just be a coincidence:

I tried some example code yesterday, though today I am working with my own code unrelated to it. Is there some kind of security or setting that can cause this? Thank you so much for your time. I feel lost without Debug!

[bbasberg]

It's me again :-) I have another clue:
Originally I had this line to begin the Function:

Public Function ProcessFileImport(ByVal sFile As String, ByVal sTable As String) As String

If I change it to:

Public Function ProcessFileImport()

I can Debug..Step Into

Could someone please explain to this newbie why I cannot "step into" when I am not using a function with parameters and can when using an ordinary procedure without variables passed in?

Thanks!!

[Killer42]

...Could someone please explain to this newbie why I cannot "step into" when I am not using a function with parameters and can when using an ordinary procedure without variables passed in?

Hm... that is a weird one, isn't it. I can't think of any reason why the parameters would make a difference to Debug mode.

What happens if you put a breakpoint inside this routine that you can't step into?