[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]
==== SEQUENTIAL KEY (OpenInsight Specific) ====
=== At 17 DEC 1998 04:34:07PM Don Pederson wrote: ===
{{tag>"OpenInsight Specific"}}
I have been having problems with a sequential key in a an app with a two part key in OI 3.7.
The first part of the key is Min_Year and defaults to the current year, the second part is Min_Num and I have defined it as defaulting to SEQKEY. It is the first field on the form.
For some reason the seqkey counter will not advance, it stays at 1.
Any ideas??
Don Pederson
----
=== At 22 DEC 1998 09:48AM Cameron Revelation wrote: ===
Hi Don,
Are you using temp tables for test running the window?
Also, check the dictionary after saving a record - is the key information updated?
Cameron Purdy
Revelation Software
----
=== At 28 DEC 1998 01:06PM Don Pederson wrote: ===
Cameron,
Thanks for your reply.
]Are you using temp tables for test running the window?
No, I'm using the real tables.
]Also, check the dictionary after saving a record - is the key information updated?
I have checked, and it doesn't update the %SK% field of the dict.
I have another app that uses a sequential counter for the key and it works fine. But in this app, the field with the sequential counter is part of a multi-part key. Could that be the source of the problem?
Don Pederson
----
=== At 04 JAN 1999 07:38AM Cameron Revelation wrote: ===
Don,
[i]I have another app that uses a sequential counter for the key and it works fine. But in this app, the field with the sequential counter is part of a multi-part key. Could that be the source of the problem?[/i]
That sounds likely. I will see what I can find out.
Cameron Purdy
Revelation Software
[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=B521607613F55EFC852566DD00767B1B|View this thread on the forum...]]