home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.databases.paradox      To crash or not to crash, asks Borland      9,834 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 9,243 of 9,834   
   Jim Hargan to Craig   
   Re: changevalue and newvalue   
   07 Jun 08 15:15:24   
   
   From: contact@harganonline.com   
      
   On Sat, 7 Jun 2008 08:18:24 -0400, Craig wrote:   
      
   > Newvalue is triggered when a new value is entered into a field but is also   
   > called on opening.   
   According to the Help, it also triggers whenever there is a screen refresh.   
   IIUC it fires whenever the value displayed within the field object is   
   updated on the screen for any reason whatsoever.   
      
   changeValue, OTOH, fires whenever the user tells the form to change the   
   value, and that's it. Again IIUC, it flushes the *field's* text buffer,   
   placing the value into the *record's* text buffer, without posting the   
   record.   
      
   > Changevalue doesn't seem to work all the time. ... This form is a   
   > notebook and if I click on the a new tab to look at   
   > the other field, the other field has not changed.   
   This is the part that interested me. For changeValue to fire, the user must   
   explicitly tell Paradox that s/he is through editing the field -- and   
   evidently clicking on a tab doesn't do this. That is, if the user clicks on   
   another notebook tab, then clicks back, the field will still be in focus   
   and its value uncommitted. But should this really be a problem? As soon as   
   the user does something real, the changeValue will fire.   
      
      
   --   
   Jim Hargan   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca