VBA Step Into (F8) stops midway through sub

[GooberTron]

On Excel 2010 (and 2013) I am having a problem using the Step Into F8 debugging option. After I have selected the folder from the dialog it just seems to stop. Whether I debug from a calling sub or just this sub the same thing happens. Essentially it just stops after the .Show (and after I have used the dialog). Is this a known problem with debugging with dialogs? I found a few related things via Google and on here but nothing concrete. I have added a breakpoint on the next line which seems to be o.k. as a workaround but not ideal.

Dim FolderPath as String 'module level variable used in other subs

Sub GetFolder()

With Application.FileDialog(msoFileDialogFolderPicker)
    .Title = "Select folder where sheets reside"
    .AllowMultiSelect = False
    .Show
    
    If .SelectedItems.Count = 0 Then
    Else
        FolderPath = .SelectedItems(1) & "\"
    End If
End With

End Sub

 

[GTO]

It is going to, and should, "stop" after .Show - until you dismiss the dialog. Could you re-explain what seems screwy about this?

 

[GooberTron]

I mean it stops after I have used / dismissed the dialog. Seems to totally exit debug mode unless I put a breakpoint on the If line immediately after the show.

 

[GTO]

If you place the cursor in GetFolder and press F8 repeatedly, it should stop on:

If .SelectedItems.Count = 0 Then

...after the dialog is dismissed.

BTW, at least in WIN7 (though I believe in XP as well), you will want to see that the "folder" picked is a real folder. In WIN7, I can pick 'Libraries' and FolderPath is set to 'Libraries\', which I am fairly certain will fall over...

 

[GooberTron]

So stepping through it works fine for you? Weird. After dismissing the dialog my sub just runs to completion without any more highlighting / stepping. I see what you mean about trying to enforce a real folder, but the calling code just uses Dir() on the FolderPath so no obvious harm as it just won't find any .xls files I suspect.

 

[GooberTron]

Just if anyone happens to get to this thread via a search, a similar post recently had a solution to this problem. See related post;
http://www.mrexcel.com/forum/excel-questions/820189-visual-basic-applications-debugging-mode.html

The registry fix in the linked Contextures post (http://blog.contextures.com/archives/2014/09/04/excel-vba-problem-with-step-into-f8/) fixed this problem for me.