ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Manufacturing >> Can a PC cause a problem with WO scrap?
http://www.istechforum.com/YaBB.pl?num=1280258703

Message started by gtladmin on 07/27/10 at 12:25:03

Title: Can a PC cause a problem with WO scrap?
Post by gtladmin on 07/27/10 at 12:25:03

Walter is convinced a certain PC is causing problems when they go to do scrap in a WO, causing errors Finance has to fix. Anybody have any ideas? The computer has no network errors, no other errors or problems with errors in other programs, etc., no other problems related to Evo that he says are PC caused.

Title: Re: Can a PC cause a problem with WO scrap?
Post by GasGiant on 07/28/10 at 04:23:54

The only thing that might be different are some user settings. Perhaps someone needs to observe a few transactions and be a second set of eyes?

Title: Re: Can a PC cause a problem with WO scrap?
Post by dameng on 08/10/10 at 16:39:51

or have Walter or someone repeat the process on another PC to see if the same result. also test drive the process in the TestData company and see if the same result occurs or not.

Title: Re: Can a PC cause a problem with WO scrap?
Post by gtladmin on 08/31/10 at 11:07:48

Um, I can tell you the same errors don't occur with anyone else or on a different system, nor do they occur consistently on this specific system he's "accusing". I have to go with what Walter says, that it's a PC (and not the person) that's causing the problem, and investigate it. ::) Ok, so I'm asking if anyone else has experience this issue before, where a PC actually causes problems in Evo.

Title: Re: Can a PC cause a problem with WO scrap?
Post by Kelloggs on 08/31/10 at 11:27:38

Dont blame the computer,
blame the person who is using the program or the programmer

:P

Kelloggs
PD: Evo is server side application.

Title: Re: Can a PC cause a problem with WO scrap?
Post by skyywalker on 09/07/10 at 11:34:15

Yes, I've seen a workstation cause problems but never that specific.

In addition to the other great suggestions here, I'd probably try:

• Copy the ISTS folder from a working workstation or clear and reinstall the Evo client.
• If you have a server that supports Terminal Services maybe you can set your user up to try Evo right at the server...with adult supervision if the problem follows.

Can your user repeat the steps that cause the error(s)?