ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Manufacturing >> WO-A Material Lookup Error Message
http://www.istechforum.com/YaBB.pl?num=1173368781

Message started by Dale on 03/08/07 at 07:46:21

Title: WO-A Material Lookup Error Message
Post by Dale on 03/08/07 at 07:46:21

Last night, we just uploaded and installed all current patches from the website. New problem today!

Opening WO-A for an active Work Order. Clicking on materials icon produces following error message:

WARN ERR - File: WBKLOOKUP.SRC Line 388
The parentheses are unbalanced in this expression:

Screen is then locked up, takes a LONG time for Task Manager to end the TAS session

Title: Re: WO-A Material Lookup Error Message
Post by NovaZyg on 03/08/07 at 08:10:52

Dale,

What are the dates of the your BKLUGRID files (DBF, DBT and MDX)

They should be 3/01/07.

Title: Re: WO-A Material Lookup Error Message
Post by Dale on 03/08/07 at 08:40:17

I'll have our IT guy look at that and let me know.

When I stopped throwing things in frustration, and we checked further, we found the problem was confined to the one Work Order I was accessing at the time, and when we made sure no one else was in that Work Order, the problem disappeared.

Could this have been some kind of record lock problem?

Title: Re: WO-A Material Lookup Error Message
Post by Dale on 03/08/07 at 09:03:46

Our files are dated 3/8/07 - today!

Title: Re: WO-A Material Lookup Error Message
Post by aostarly on 03/13/07 at 13:24:48

I'm getting an error message as well but not the same one. I am printing the Material Issues of a work order, then I go back to the main screen. That's when I get an access violation error and have to end task to get out of the WO-A screen.

Angelle Ostarly

Title: Re: WO-A Material Lookup Error Message
Post by Dale on 03/14/07 at 03:18:03

Angelle

Our problem actually seemed to be a record lock - two people using the same data at the same time. Did not occur before or since, and only with that one Work Order.

If your problem is repeatable, make sure you take note of the "Line #" in the error message. That information is critical to the programmers for troubleshooting the problem.

Good Luck!
Dale