SEQKEY (OpenInsight 32-bit Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[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]]


==== SEQKEY (OpenInsight 32-bit Specific) ====
=== At 19 JUL 2003 11:19:34AM Bob Silverstein wrote: ===
 
{{tag>"OpenInsight 32-bit Specific"}}
 
<QUOTE>
How do you implement "SEQKEY" for the record key in forms?  Could not find anything in the documentation.  Thanks.
</QUOTE>
----

=== At 19 JUL 2003 11:53AM Donald Bakke wrote:  ===

<QUOTE>Bob,



In the Properties dialog for your Key ID control just select SEQKEY from the Default combo-box.



dbakke@srpcs.com

[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]



[img]http://www.srpcs.com/srpicon1.gif[/img]

</QUOTE>

----

=== At 19 JUL 2003 01:20PM Bob Silverstein wrote:  ===

<QUOTE>I was surprised to get an answer so quickly on a Saturday.



Don, I have just done that and the key field remains blank.  I must have some other script interferring with SEQKEY.  How do I specify the key?  In AREV, %SK%  did the job.

</QUOTE>

----

=== At 19 JUL 2003 01:46PM Donald Bakke wrote:  ===

<QUOTE>Bob,



SEQKEY in OI works the same way it does in AREV. That is, the %SK% record in DICT.[i]TableName[/i] holds the next default sequential key. However, you can't enter the "= character to change the value of this key (at least, not without additional programming.)



Normally you should get a message box asking you for the first sequential key value. It does seem like something is causing the default not to fire. If you have a GOTFOCUS script event on this control that is returning a 0 then this will prevent the default logic from firing.



dbakke@srpcs.com

[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]



[img]http://www.srpcs.com/srpicon1.gif[/img]

</QUOTE>

----

=== At 19 JUL 2003 07:22PM Richard Bright wrote:  ===

<QUOTE>Bob, If Don's suggestion doesn't get things rolling ... (perhaps the %SK% key hasnt been created in the table dict) ... Using the Table Builder - bring up the Dict table in question, key value and put in SEQKEY as default.  Then recompile window.



Richard Bright

BrightIdeas New Zealand

</QUOTE>

----

=== At 21 JUL 2003 07:48AM Bob Orsini wrote:  ===

<QUOTE>Bob



If you have a create event on the window try sending a gotfocus to the key control. 

</QUOTE>

----

=== At 22 JUL 2003 09:56AM Dave Harmacek wrote:  ===

<QUOTE>I suggest you NOT use SEQKEY and code a button or allow "N" to trigger the entry of the next, unused sequential key.



This way multiple users don't have the same next, unused value sitting as the default where it is possible to lose data when the "last" Save overwrites a previous Save on another workstation.



Dave

</QUOTE>

----

=== At 22 JUL 2003 11:53AM Don Miller - C3 Inc. wrote:  ===

<QUOTE>Agree completely.  The SEQKEY (SK%) problem has been around since the year dot and there have been a good many replacements for it over the years (REV,AREV and OI).  In fact, I think OI may be less stable in this regard than others.  Anyway, it's easy to code around.  



Don M.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=70B120F1583C040685256D68005430B7|View this thread on the  forum...]]