Another option may be to do some kind of cut-down select to get a count or 
some indication of volume/rows that will be returned, and then display a 
messagebox to the effect "This will retrieve xxxx rows. Continue?". I have 
done this and found it suites my purpose, as long as the SQL for the count 
runs quickly.

Gary Hyland

-----Original Message-----
From:   Stella Kravchenko [SMTP:[EMAIL PROTECTED]]
Sent:   Saturday, August 28, 1999 6:16 AM
To:     [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject:        Re:RE: RE: Re[2]: PFCSIG Cancel retrieval and Hourglass

This is how I finally implemented it also, but as Russ mentioned, "Cancel 
take
place at the end of the end of the select during the fetch", so it does not
cancel right away and still returns first row or 'no rows returned'.

Thanks,
Stella
____________________Reply Separator____________________
Subject:    RE: RE: Re[2]: PFCSIG Cancel retrieval and Hourglass
Author: [EMAIL PROTECTED]
Date:       8/27/99 4:37 PM

This works fine for me. This is how I have implemented it.

I have a progress window with  cancel retrieval command button.  The window 
is
opened in retrievestart event. It's closed in retrieveend and clicked event 
of
the cacel button.

In constructor event of n_cst_appmanager nvuo, I have
SQLCA.dbParm = "Async = 1"

In clicked event of cancel query command button,
window_name.data_window.dbcancel()





[EMAIL PROTECTED] on 08/27/99 02:25:00 PM
To:     [EMAIL PROTECTED]@Internet,
[EMAIL PROTECTED]@Internet, [EMAIL PROTECTED]@Internet,
[EMAIL PROTECTED]@Internet
cc:      (bcc: Leena Daptardar/Americas/NSC)
Subject:        RE: RE: Re[2]: PFCSIG Cancel retrieval and Hourglass

For long waits you are not supposed to use an hourglass, but instead some
sort of progress window.

        Russ

-----Original Message-----
From: Stella Kravchenko [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 27, 1999 12:15 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re:RE: Re[2]: PFCSIG Cancel retrieval and Hourglass


You have a point, but imagine a long retrieve when rows do not come back
right
away and user sits in front of the computer and there is no activity  and 
no
hourglass.  Hourglass indicates that there is process running.  I have not
decided yet, but as was suggested, my best bet could be a popup window with
Cancel button.

Thank you,
Stella

____________________Reply Separator____________________
Subject:    RE: Re[2]: PFCSIG Cancel retrieval and Hourglass
Author: [EMAIL PROTECTED]
Date:       8/27/99 7:25 AM

First Union Capital Markets Corp.

It doesn't make sense to me that you would want to show an hourglass 
pointer
at a time when a user is allowed to click on a button.  The hourglass
pointer is an indication that the user must wait for an operation to
complete before they can do anything.

We've implemented cancelable retrieves in the past, and were happy to see
the hourglass disappear when it did.  Are you sure you really want to do
this?

BTW, I'm not trying to get into a philosophical argument here.  I respect
any opinions that oppose mine on this.  No need to straighten me out.

Thanks.

Scott Daggett      704-593-7035 work    704-354-9539 beeper

-----Original Message-----
From:   Daniel Coppersmith [SMTP:[EMAIL PROTECTED]]
Sent:   Thursday, August 26, 1999 9:39 PM
To:     Stella Kravchenko; PFCSIG
Subject:        Re: Re[2]: PFCSIG Cancel retrieval and Hourglass

Have you tried to put SetPointer(HourGlass!) in the retrieveRow event
itself?

----- Original Message -----
From: Stella Kravchenko <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, August 26, 1999 5:58 PM
Subject: Re[2]: PFCSIG Cancel retrieval and Hourglass


> Let me explain a little bit.  I have put SetPointer(Hourglass!) before 
the
> retrieve. And hourglass stays until the retrieve is done if I do not code
> RetrieveRow event.  In order to cancel the retrieve, I need to return 1 
in
the
> RetrieveRow event if user clicked on Cancel button. Here is a sample code
that I
> have in the RetrieveRow event:
>
>  if ib_cancel then return 1
>
> As soon as I code anything (even comments) in the RetrieveRow, the
Hourglass is
> gone.
> Any other ideas?
>
> Appreciate your help,
> Stella
>
>
> ____________________Reply Separator____________________
> Subject:    Re: PFCSIG Cancel retrieval and Hourglass
> Author: [EMAIL PROTECTED]
> Date:       8/26/99 4:57 PM
>
> Have you tried    SetPointer(HourGlass!)
>
>
> ----- Original Message -----
> From: Stella Kravchenko <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Thursday, August 26, 1999 3:50 PM
> Subject: PFCSIG Cancel retrieval and Hourglass
>
>
> > Hello everybody,
> >
> > I have a problem canceling retrieve on a dw and displaying an Hourglass
> until
> > cancel happens. We have some long retrieves that users would like to
> cancel.  In
> > order to cancel the retrieve, I need to have a code in the Retrieverow
> event of
> > the dw.  This code wipes out the Hourglass! pointer that otherwise 
would
> show
> > while the retrieve is in progress.  Does anybody experienced same
problem
> or
> > maybe someone has solution/workaround for that.
> > I need to solve this either with or without the PFC ASAP. Please help!
> >
> > TIA,
> > Stella
> > > [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE
COMMANDS,
> ADDRESS
> > > A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE:   help
> pfcsig
> > > SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
> >
>
> > [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS,
ADDRESS
> > A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE:   help
pfcsig
> > SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
>

> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS,
ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE:   help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS,
ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE:   help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS,
ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE:   help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]


> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, 
ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE:   help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]

> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE:   help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]

Reply via email to