Hi Dion,

Here are a couple of questions...

Why not initiate your 'update' code from the pfc_preclose event? 

I am curious about why you are updating the datawindow in the save event.
Obviously it can't be something for the users to see, so if you have a DBMS
that can support stored procedures why not perform that function on the
DBMS?

Sheldon

> -----Original Message-----
> From: Wirrenga, Dion W. [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 07, 2000 11:02 AM
> To:   '[EMAIL PROTECTED]'
> Subject:      PFCSIG Missing updates during close process
> 
> Has anyone found a work around for the following situtation?
> 
> I overrode the pfc_save event to do some updating of my datawindow and
> then
> I call the Super.  The problem happens when the window is closed without
> saving changes first.  What happens is that the pfc_close process builds
> an
> array of objects with updates pending and if the array contains any
> objects
> the prompt is sent asking if I want to save my changes before closing.  If
> I
> respond with 'yes', the pfc_save event fires, my code is executed which
> does
> updates to the dw and then I call the super.  The ancestor script for
> pfc_save checks to see if the close is in progress, and it is in this
> case,
> so the array of updateable objects is not rebuilt.  This is a problem for
> me
> because my dw did not have any changes pending when the window was closed
> but now does because of my code in the pfc_save event, so my dw doesn't
> get
> in the update sequence.
> 
> I need a way to get my updates ahead of the save process.  Any
> suggestions?
> 
> Thanks.
> 
> Dion W.
> 
> 
> 
> > [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