Kbase P25652: Error# 3589 with CURRENT-VALUE statement, NEXT-VALUE and CUR
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  5/22/2003 |
|
Status: Unverified
SYMPTOM(s):
Attempting to run the Progress NEXT-VALUE 4GL Function.
Attempting to execute the Progress CURRENT-VALUE 4GL Function or Statement.
Sequence ambiguity for <sequence>. Exists in databases <dbname> and <dbname>. (3589)
CAUSE:
The sequence whose value is being manipulated exists in more than one connected database. The CURRENT-VALUE statement and the NEXT-VALUE and CURRENT-VALUE functions have an optional parameter that specifies the logical name of the database in which the sequence is defined. This parameter cannot be omitted if the sequence name is ambiguous amongst two different databases.
FIX:
Use the logical-dbname identifier within the CURRENT-VALUE statement or the NEXT-VALUE and CURRENT-VALUE functions. e.g.:
ASSIGN CURRENT-VALUE(NextCustNum,sports2000) = 100.