Welcome, Guest. Please Login.
05/19/25 at 04:36:25
Welcome to IS Tech Support Forum for Evo-ERP and DBA Users
Home Help Search Login


Pages: 1
Send Topic Print
WO #'s dont scan like they did in 6/20/05 update (Read 244 times)
kevind
Active Member
*****


I was more than
willing to
"pony up",
how b'out U?

Posts: 634
Gender: male
WO #'s dont scan like they did in 6/20/05 update
09/28/06 at 13:43:10
 
Just updated to 8/11/06.  We use barcode scanning for
Data collection.   Our WO Numbers are generally in the  
form 501555-1.  
 
In update 6/20/06 we could scan the WO barcode without
any problem.  In 8/11/06, the 1 is not being recognized.
 
Has anyone else had or solved this problem
 
While trying to diagnose this problem, I changed the barcode  
scanner to add a 50ms delay between characters.  This
still results in the numbers after the '-' being dropped.
 
The WO # 501555-1 is represented in the barcode as
501555001.   The 001 is dropped when the program
changes from the 6 digit input field to the 3 digit input field.
We have been using data collection for several
years now.  It has always worked until now.
 
 
Back to top
 
« Last Edit: 10/02/06 at 08:33:03 by kevind »  

Kevin Damke
Spectronics Corporation
ISTECH 2004.1 7/26/13 SP1 - 20 user
Evo-ERP Build 7/25/13 T7 -7i R6 - 3 user
(Prev version was 2004.1 10/24/12)
(All Patches Installed as of 7/26/13)
Pervasive 2000i SP4 - Crystal Reports V10
Email WWW   IP Logged
Pages: 1
Send Topic Print