Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Keyboard freezup
Message
De
13/08/1997 12:49:54
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Divers
Thread ID:
00044448
Message ID:
00044474
Vues:
35
>>>>One of our departments uses a wand to scan in a barcode representation of a Social Security Number. (999-99-9999)
>>>>The entry field also contains the following code in the keypress event:
>>>>
>>>>if nkeycode = 134 then &&F12
>>>> thisform.F12search
>>>>endif
>>>>
>>>>The problem is, every once in a while, when scanning in a SSN, the program completely freezes up. I suspect that this is because it is trying to execute the preceding code in between every key, and the program thinks that the keys are being pressed too fast. If this sounds legitimate, how can I work around it? If not, what could be causing the screen to lock up? This is a very urgent problem, as this a very high volume screen and the problem is causing serious delays. Thanks in advance for any help you can give.
>>>>
>>>>Erik
>>>
>>>Text.KeyPress Code itself shouldn't freeze the form. Maybe you fire Form.KeyPress event (check Form.KeyPreview property).
>>
>>There is no code in the form.keypress, and form.keypreview = .F. This only happens when the scanner is being used, and not from the keyboard. The scanner sends keyboard data in a very quick stream after the barcode has been completely scanned. Any other ideas on what couls be causing this?
>>
>>Erik
>
>I do know scanners usually issue an automatic *Return*, and SET CONFIRM OFF can be resulting in an "extra" return being issued if the scanned field is filled. If this is not what you intended, it could produce undesirable results.

Yeah, I was aware of that, but I had to learn that the hard way also. I don't think it's causing the problem. Another hint... when scanning in the SSN, the computer issues a series of beeps, like the ones you get when you hold a key down in DOS for a long time. I'm guessing sort of a keyboard buffer overflow warning, but it does this even when the screen doesn't freeze up, and the data gets into the field just fine. I'm getting flustered here.

Erik
Erik Moore
Clientelligence
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform