Ken, I agree with most of what you've mentioned here when it comes to touchscreen input and VFP.

Do you realize that the "Native Options buttons" can be changed to be "Graphical" and when styled this way, you can make them as large as you wish to accommodate those fat fingers?

Any serious data entry requires a real keyboard (hardware). For simple input on a touchscreen, you can use the one that comes with Windows (osk.exe) or make your own. I did the latter since osk.exe was overkill for what I needed.

My 2cents (BTW, I typed this using osk.exe. What a pain! :)

Mike

>>It is most likely button driven, however looking at the spec I've been given, there will be times when keyboard may be necessary.
>>
>>I like to use combo boxes, etc to choose from when keyboard is necessary to trap for incorrect response. Can I use comboes etc?
>>
>>Bar code is not part of the option at this time. (I wish it was, I know a lot about that technolohy...)
>>
>>TIA,
>>Mike
>
>Hi Mike,
>
>Native combo's are a problem because they do not "size" very well. Touch screens need large controls. You can make the combo font large but the dropdown arrow remains pretty narrow. Native Option buttons are even worse. We have written our own so they can have a decent size needed for fat fingers on a touch screen.
>
>You might consider using a grid instead of a combo. There you can have large size row heights and you can make them multi coice by adding a column with a graphic checkbox.
>
>Keyboard input is a pain. We let them use a regular keyboard. If that is not an option I believe thare are some 3rd party controls out there.
>
>Another problem is "right clicking" The POS-X touch screens I use come with software that puts a mouse graphic on the screen so you can right click.
>
>
>As far as touch screens go, I use POS-X. They have been very reliable and at a reasonable cost. I retail them for $460 to my POS users.
>
>HTH,
>
>Ken