Microsoft KB Archive/126099

{|
 * width="100%"|

BACKSPACE Key Sent Twice Using SendKeys Statement in Procedure

 * }

-

The information in this article applies to:


 * Microsoft Excel for Windows, versions 5.0, 5.0c

-

SYMPTOMS
In Microsoft Excel, when you use the SendKeys statement to send the BACKSPACE keystroke to the active window, each backspace code ({BACKSPACE}, {BS}, or {BKSP}) in your procedure may send the BACKSPACE keystroke twice instead of one time as expected.

CAUSE
This problem only occurs when you run a procedure that uses the SendKeys statement to send the BACKSPACE keystroke while the active window is a Visual Basic module or the Immediate pane in the Debug window in Microsoft Excel.

Note that this problem does not occur in Microsoft Excel for Windows NT or Microsoft Project.

WORKAROUND
To work around this problem, use the SendKeys method, instead of the SendKeys statement, as in the following example:

Microsoft provides examples of Visual Basic for Applications procedures for illustration only, without warranty either expressed or implied, including, but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. The Visual Basic procedures in this article are provided 'as is' and Microsoft does not guarantee that they can be used in all situations. While Microsoft support professionals can help explain the functionality of a particular macro, they will not modify these examples to provide added functionality, nor will they help you construct macros to meet your specific needs. If you have limited programming experience, you may want to consult one of the Microsoft Solution Providers. Solution Providers offer a wide range of fee-based services, including creating custom macros. For more information about Microsoft Solution Providers, call Microsoft Customer Information Service at (800) 426-9400.

  Sub Test 'abc Application.SendKeys "{UP}{HOME}+{END}{DEL}{BS}"

End Sub

STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.