Visual Basic 6 & Access 2000

[Luciano]

Hi,

Normal windows programs

When a key is pressed, the keyboard driver passes the keystroke
to Windows and the message is saved in the system message queue.
Windows then transfers the message from the system queue to the
queue of the program with the "input focus" where the keystroke
is then processed.

* * *

Games using DirecX

DirectInput (see DirectX) works directly with the keyboard driver.
So when you play, the game does not get keystrokes as a normal
Windows message.

* * *

Be aware that posts in forums can be very old. (Not about VB6 SP6).
Also most of these post are written by people like me and you.

Best regards,

Luciano

[Demon]

I'm still not sure how DirectInput games will come into play with my machine. I guess I'll have to cross that bridge when I fall in the water. I suppose I can learn about DirectInput later and add in code to deal with those games at that point. I'll add a flag right away in my database; Input Type (DirectInput or Keyboard Input).

I tried that guy's demo, pasted the Class Module directly in my project, I called his version of SendKeys with "{LEFT}" and the Left Arrow worked like a charm in my game.

WOOHOO! I'm back on track.

Robert

[Demon]

Lots of small debugging completed. I've found out the importance of nulls and properly initializing fields.

One thing is odd, the custom SendKeys logic above works like a charm except for one thing:

^%{DELETE}

I would have expected the Task Manager screen to pop up but apparently it doesn't work that way. Is there some sort of parameter that disables CTRL-ALT-DELETE by default or something like that?

Robert