<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>What about the edit procedure?<br>
<br>
</tt><br>
Ken Langendock wrote:
<blockquote cite="mid003b01c7a921$b91e15c0$0c01a8c0@kenlangendock"
type="cite">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.6000.16441" name="GENERATOR">
<div dir="ltr" align="left"><span class="203483216-07062007"><font
color="#0000ff" face="Arial" size="2">Yes, however the OUTPUT
procedure fires every time a refresh or find is invoked.</font></span></div>
<div dir="ltr" align="left"><span class="203483216-07062007"><font
color="#0000ff" face="Arial" size="2">I was trying to get something
that only fires after an ACCEPT or PROMPT is complete.</font></span></div>
<div dir="ltr" align="left"><span class="203483216-07062007"></span> </div>
<div dir="ltr" align="left"><span class="203483216-07062007"><font
color="#0000ff" face="Arial" size="2">Ken</font></span></div>
<div dir="ltr" align="left"><span class="203483216-07062007"></span> </div>
<div dir="ltr" align="left"><span class="203483216-07062007"></span> </div>
<br>
<div class="OutlookMessageHeader" dir="ltr" align="left" lang="en-us">
<hr tabindex="-1"><font face="Tahoma" size="2"><b>From:</b> Michael
Lee [<a class="moz-txt-link-freetext" href="mailto:mcl_systems@telus.net">mailto:mcl_systems@telus.net</a>] <br>
<b>Sent:</b> June 7, 2007 12:25 PM<br>
<b>To:</b> Ken Langendock<br>
<b>Subject:</b> [Bulk] Re: New Features - PREINPUT<br>
</font><br>
</div>
I like the pre-input procedure idea.<br>
<br>
Isn't the postinput procedure just like the output procedure?<br>
<br>
<br>
Ken Langendock wrote:<br>
<blockquote cite="mid002c01c7a91e$583c5350$0c01a8c0@kenlangendock"
type="cite">
<meta content="MSHTML 6.00.6000.16441" name="GENERATOR">
<div><span class="000030216-07062007"><font face="Arial" size="2">You
asked for it Bob.....</font></span></div>
<div> </div>
<div><span class="000030216-07062007"><font face="Arial" size="2">A
procedure that fires right before the Prompt or Accept procedure would
be easier to use than hard coding a Entry, Path or Designer procedure.</font></span></div>
<div> </div>
<div><span class="000030216-07062007"><font face="Arial" size="2">This
can be used for the following:</font></span></div>
<div> </div>
<div><span class="000030216-07062007"><font face="Arial" size="2">1)
Information messages for the user to see as they are prompted.</font></span></div>
<div><span class="000030216-07062007"><font face="Arial" size="2">2)
In the new QKView product, it allows us the ability to turn on a
function key label before the user is prompted for a field that has a
function key feature.</font></span></div>
<div> </div>
<div><span class="000030216-07062007"><font face="Arial" size="2">This
might also make a case for a POSTINPUT procedure, that fires when a
user leaves a field. This would be similar to the POSTUPDATE procedure
except it would fire regardless of the fact the user entered a value in
the field or not.</font></span></div>
<div> </div>
<div> </div>
<div><span class="000030216-07062007"><font face="Arial" size="2">Ken</font></span></div>
<div> </div>
<div> </div>
<img src="cid:part1.01070101.02000907@isu.edu"
v:shapes="_x0000_i1025" height="186" width="317">
<div> </div>
</blockquote>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Richard Sheehan
Computer Analyst, Senior
208-282-4430
Office of Institutional Research
Idaho State University
Pocatello, ID 83209-8368
</pre>
</body>
</html>