Sendkeys doesn't work on my laptop with Vista

**foxguy** · 01-25-2010, 03:29 PM

I have a workbook that I transfer back and forth from my desktop to my laptop, that uses Sendkeys to add code to the active pane in VBA. It doesn't work on my laptop, but works fine on my desktop.

Both computers have Vista. Is there a switch somewhere to make Sendkeys work?

**romperstomper** · 01-25-2010, 06:05 PM

Is this just to save typing, as a matter of interest?

**foxguy** · 01-25-2010, 08:04 PM

Yes, primarily from having to type the same stuff over & over.

**Leith Ross** · 01-25-2010, 11:29 PM

Hello foxguy,

SendKeys under Vista seems to be problematic, especially when run in the VBIDE. Your best option is to use an API code replacement for SendKeys. I would need to see samples of the data you're sending before I could offer the best solution.

**foxguy** · 01-26-2010, 05:36 PM

Leith;
It's news to me that SendKeys under Vista is problematic, but it explains my problem.
I have 2 situations. The 1st I can fix by using the codemodule methods, but the 2nd stumps me.

Sub SomeSub()
    .... codelines
    MyStop
    .... more codelines
End Sub

Sub MyStop()
    If IsDeveloper() then
        Application.Sendkeys "+^{F8}"                'Step Out (back to calling procedure)
        Stop
    End If
End Sub

This lets me put in just one word "MyStop" in my code that stops and positions my cursor on the next line after MyStop, and I don't have to worry about accidentally leaving it in the finished product, because IsDeveloper() never returns TRUE except on my computer.
This works fine on my desktop, but on my laptop, it stops inside MyStop and I have to manually click on "Step Out". Just irritating, and I would rather not live with it.

Any ideas on how I can make this work the way I want?

**romperstomper** · 01-26-2010, 05:47 PM

What's wrong with breakpoints or Run to Cursor? Either would be better than adding unneeded code to a project, IMO.

**romperstomper** · 01-26-2010, 06:57 PM

In fact, if IsDeveloper is only true on your machine, why not just use a:

Debug.Assert Not IsDeveloper()

statement?

**foxguy** · 01-26-2010, 07:24 PM

Romperstomper;
I admit, I forgot all about Assert. It accomplishes the same thing, just more typing.

My sub is actually named MS(), so that I only have to type 2 letters to put in a conditional stop. I hate typing in the same code over & over, which is why I developed the subs that insert code into the codepanes in the first place.

It looks like I'll developer a sub that inserts "Debug.Assert IsDeveloper()" into my code. I'll just have to get used to hitting a menu button instead of typing "MS".