![]() I'll have to mung around a bit with the code, but it's better than using the KeyUp event. I think for right now using the Change event would be a better alternative. Although I haven't tested this exhaustively by any means, it looks as though the KeyUp event doesn't fire for the Delete key *if* pressing it deletes selected text from the text box. I'm seeing similar behavior in Access 2003. The text box, the Change event would seem to be suitable.Īccess tips: I sure hope this is an Access 2007 bug with a fix because I don't look forward to a kludge to fix this problem.Īccess tips: Interesting. The KeyUp event seems to fire if the key is pressed with no characters selected, whether it results i the deletion of a character or not.Ĭan you use the text box's Change event instead of the KeyUp event as a workaround? The Change event will fire whenever user action (keystroke, paste, or cut) modifies the. The KeyDownĮvent does seem to fire under those circumstances. The "ABC" is deleted but the KeyUp event does not trigger!!!!!.I have tried SendKeys method as well but it cannot differentiate between KeyDown and KeyUp separately. I can't fire the KeyDown and KeyUp events from any external program. But the problem which I m facing, is at the time of playing those stored keystrokes. Type Shift-Home which highlights/selects the text "ABC" As of now I have successfully captured the keystrokes and stored those strokes.I have a TextBox and an OnKeyUp event so that I can process what has been typed in after each keystroke using the TextBoxA.Text properties. I sure hope this is an Access 2007 bug with a fix because I don't look forward to a kludge to fix this problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |