By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,292 Members | 1,758 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,292 IT Pros & Developers. It's quick & easy.

Problems with Access 2003 - Keyboard Type Ahead Buffer

P: n/a
The keyboard type ahead buffer does not seem to work in Access 2003 in
certain situations. We would like some help with this.

Here are the details.

We have a large program that was developed in Access 2000. We are now
converting it to Access 2003.

The program has a form for entering orders. Each order usually consists
of dozens of items. To enter the items on the order the entry person
only enters the quantity and a 4-digit number that corresponds to the
product. The entry people use the number pad and are very fast.

The entry form does some validation behind the scenes which does not
take long, but the entry person can go faster than the code in the
form. In Access 2000 this was not a problem because when the entry
person got ahead of the form the keystrokes were saved in a buffer and
when they finished typing the entire order it would take just a second
or two for the program to catch up.

However, in Access 2003 we are having problems because the keystrokes
are not saved in the buffer. They are lost. Therefore, wrong quantities
get entered and wrong products are selected. As a result the order
entry people have had to really slow down which may cause the need for
some overtime work.

The program uses an MS Access "Project" (*.ADP and *.ADE) and links to
a SQL Server 2000 database. Any ideas you have as to what causes this
and what can be done to fix it will be appreciated. Is there perhaps
some new security feature of Access 2003 that does not allow keystrokes
to be saved in a buffer?

Thanks....

Nov 13 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.