TT5 Prompts and Error Messages

To answer your questions, yes and no respectively.

Regards Chris Reed
PWSL


-----Original Message-----
From: JKroes@... [mailto:JKroes@...]
Sent: Monday 05 March, 2001 17:43
To: vantage@yahoogroups.com
Subject: [Vantage] TT5 Prompts and Error Messages


We are implementing bar code labor data collection. We are now at
4.00.904. My problem is that the prompts and error messages go by so
fast they can't be read. Sometimes they don't even change the
display. Messages like "Invalid employee number" and "Already
Clocked In" can save a lot of frustration on the part of the
employees, but they never see them because they move so fast.

I have already tried changing the prompt timing parameter in the gate-
prm.txt file. For some reason, this timer runs before the prompt
displays instead of after. I set it to 10000 (10 seconds) and I get
a 10 second pause before the "Clock In" prompt is displayed so
quickly you can barely see it. This parameter does not affect error
messages at all.

I have been through this with Epicor support, but they have no real
answer. Has anybody else been through this? Is there a fix?

Thanks in advance,

Jeff Kroes
Pacal Industries
We are implementing bar code labor data collection. We are now at
4.00.904. My problem is that the prompts and error messages go by so
fast they can't be read. Sometimes they don't even change the
display. Messages like "Invalid employee number" and "Already
Clocked In" can save a lot of frustration on the part of the
employees, but they never see them because they move so fast.

I have already tried changing the prompt timing parameter in the gate-
prm.txt file. For some reason, this timer runs before the prompt
displays instead of after. I set it to 10000 (10 seconds) and I get
a 10 second pause before the "Clock In" prompt is displayed so
quickly you can barely see it. This parameter does not affect error
messages at all.

I have been through this with Epicor support, but they have no real
answer. Has anybody else been through this? Is there a fix?

Thanks in advance,

Jeff Kroes
Pacal Industries