improvement
There's somewhat of an improvement. Still takes longer than my user's patience. This is a program for our receiving department.
FIND LAST WhseBin
WHERE WhseBin.Company = CUR-COMP
AND WhseBin.WarehouseCode = "ASP"
NO-LOCK.
DO WHILE LENGTH(WhseBin.BinNum) <= 4...
Opps it's actually >4
Good catch, but my code actually says ">4". That being said if I run the code without my exclusions I'll get the last number as being "U5021".
Sorry for my mistake.
FIND LAST WhseBin WHERE WhseBin.Company = CUR-COMP AND WhseBin.WarehouseCode = "ASP"
AND...
I've got a bin # table that has about 26,000 records in it(A001 TO Z963). We recently changed our bin numbering system to start with AA001. Also in the bin record there are a few erronious entered bin#s.
It's taking too long to find that last record. Below is my snippet of code. Is...
what I've found
There is a known bug in Clienttimeout with Progress 9.1C. I found this out from my software vendor. Has anybody discovered a workaround for this? I'm using the Vantage manufacturing package produced by Epicor.
We are currently trying to upgrade from Vantage 4.0 (using Progress 9.0B) to Vantage 5.1(using 9.1C). Whent the Clienttimeout is added to the registry key for HKeylocalmachine it crashes the database.
Does anybody have any insight into this?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.