Running QTP from QUICK

[Oran Shapitka]

It seems to me that I have done this in past using a TEMPORARY <field name>
RESET AT STARTUP.  I believe I had to place the temporary item as part of
the ACCESS <file> VIA <key/index> USING <temporary item>.  I don't recall if
I also needed to use the temporary field on the screen for input, and then
use an ITEM statement to assign the temporary value into the actual field of
my primary file.  I used a PUSH FIND as part of the POSTUPDATE procedure.  I
know I didn't touch the PATH procedure.

Unfortunatly I don't have a sample of the code available, and I don't have
time at present to write and test a sample for you.

Hope that this might give you another idea to try out.

Oran Shapitka, ISP
Intertech Business Systems, Inc.
1564, 10303 Jasper Ave		 Email:  oran@intertechsystems.com
Edmonton, AB  T5J 3N6  Canada	 Voice:  (403) 413-0400	Fax:  (403) 413-0398

> -----Original Message-----
> From: owner-powerh-l@sphere.swau.edu
> [mailto:owner-powerh-l@sphere.swau.edu]On Behalf Of pickerij@norbord.com
> Sent: Tuesday, January 12, 1999 10:29 AM
> To: kaffenbe@karmanos.org; powerh-l@lists.swau.edu
> Cc: bob.deskin@Cognos.COM
> Subject: RE: Running QTP from QUICK
>
>
> >We have a QUICK application that runs a series of QTP batch edits.
> >The QTP edits used to be read only, but now have been changed
> >to update one field based upon certain conditions.  When control
> >is returned to the QUICK program and this field has been updated
> >and the user tries to make a change, it displays the message
> >'Record has changed since you found it'.
> >
> >We have considered different ways to get around this, but everything
> >we look at entails lots of programming effort.   What we really want to
> >do is when control returns from QTP to QUICK, we want to refind and
> >redisplay the current record.
> >Is this possible?
> >
> >PH 7.29.C8 MPE/ix 5.5
>
> Yet another customer who needs my enhancement request to allow the PUSH
> verb to push a string of data onto the stack. With this you could push
> the key value and the FIND command and retrieve the same data again. I
> keep harping on this enhancement in the hopes that someday Cognos will
> listen.
>
> Without it you've got some programming to do! I usually accomplish this
> sort of thing by either pushing just FIND or NEXT and letting the user
> re-enter the key value (which usually makes then very happy :-) or by
> putting a ghost screen in front of the real screen and passing the key
> value back and forth. The real screen then needs to use the
> passed value
> if it isn't blank or prompt for it if it is. The ghost screen passes a
> blank value in the first time and then looks at what it gets
> back. If the
> returned value is blank then it exits, otherwise it runs the real
> screen
> again. This usually requires messing with the PATH and FIND
> procedures a
> bit.
>
> All of which work could be saved by enhancing the conditional command
> list to allow text strings!!! Have I said that before?
>
> Regards,
> John Pickering
> JWP Systems Inc
> Toronto
>
>
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> = = = = =
> Subscribe: "subscribe powerh-l" in message body to
> majordomo@lists.swau.edu
> Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
> powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> This list is closed, thus to post to the list, you must be a subscriber.
>
>

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.