D
David Geiger
We have a large program that was developed in Access 2000. 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 which corresponds to the product. The entry people use the
number pad are very fast. They do not look at the screen because there is a
checking process later. 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 key strokes 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 key strokes 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?
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 which corresponds to the product. The entry people use the
number pad are very fast. They do not look at the screen because there is a
checking process later. 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 key strokes 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 key strokes 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?