From: mynamehere@comcast.net   
      
   "Joe-Paul"  wrote in message   
   news:uvSdnWSmrtqIxiDfRVn-uA@comcast.com...   
   > "Steve Gerrard"  wrote in message   
   > news:7uidnTX5e_GNYSHfRVn-iw@comcast.com...   
   >>   
   >> "Joe-Paul"  wrote in message   
   >> news:1cidnf6EwfJ_RiHfRVn-qQ@comcast.com...   
   >>>   
   >>> If I put code in the Before_Update event checking for the required data and   
   >>> the data isn't there, I can do "Cancel = true"...then I get a message that   
   >>> says "Action is Cancelled"... It doesn't allow me to put in my own message.   
   >>> I can use vbdataerrcontinue, and the error message is not shown,   
   >>> but the record is saved.   
   >>>   
   >> I think you need to trap the "Action is Cancelled" message in the Error   
   event   
   >> of the datagrid, set the Error event's Response parameter to 0   
   >> (vbDataErrContinue), and do your message there.   
   >>   
   > I've used the vbDataErrContinue and the message is suppressed.  But the   
   record   
   > is still saved.  I don't want it to save that record.   
   >   
   > JP   
   >   
      
      
   Don't use vbDataErrContinue in the BeforeUpdate event. Setting Cancel =   
   vbDataErrContinue is the same as Cancel = False, hence the record is saved.   
      
   Set Cancel = True. Then in the Error event, set Response = vbDataErrContinue.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)