>Hello Ian,
>
>I have a possible solution, although not as generic as Ed Rauh's. My solution depends on whether your client needs this inside some software that you wrote (or have control over).
>
>What I have is an on-screen keyboard form and command button class, developed for use IN A TOUCH SCREEN APPLICATION. The form itself has no code, just instances of the button class. This could EASILY be made into a small DLL where the form was called with a method and the resulting keyed string was stored in a property for use by whatever could see the DLL.
>
>Don't know if this will work for you, but let me know if it will help.
>
>Evan Pauley
>
>
>Ian Sizer wrote:
>>Hello!
>> I have a client that works on point of sale terminals and networks, and he is complaining that he often finds himself without a keyboard, and hence the ability to modify files or workgroup names etc. because the terminals (running in Windows) use a touch screens.
>>What he has requested is a program that would respresent a keyboard on the screen so that he could peck away at various things. The problem I have is I don't know how to send strings to active programs. Such as notepad and neighborhood networking properties.
>>Any suggestions?
>>
>>Thank you very much in advance,
>>Ian Sizer

Are you offering to post the form and button class? If you are I'm interested. :)