Yeah, that's what Doug suggested in an earlier post, but we did not change anything about the underlying DB when we upgraded.
What leads me to believe that it's a Remedy thing and not a SQL thing is that this code ran faithfully without incident for over two years in 5.1.2. Then we upgraded to 6.3 (again, we did not touch the underlying DB), and BAM! It stops working. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Warren Baltimore Sent: Thursday, June 14, 2007 2:22 PM To: [email protected] Subject: Re: $NULL$ != $NULL$ ** I'm not really sure about this, but I think this is actually how SQL handles null=null...Not so much a Remedy thing... Any SQL gurus out there care to explain this one? On 6/14/07, Opela, Gary L Contr OC-ALC/ITMA <[EMAIL PROTECTED]> wrote: ** What they will say is that they have fixed a bug, not that they've broken your code. I have run into this in the past, where I had to write remedy functionality designed around, or using their bugs, then they fix it and break the functionality. Some bugs, I guess, are just best left in the product. ________________________________ From: Action Request System discussion list(ARSList) [mailto: [EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CS/SCCE Sent: Thursday, June 14, 2007 8:26 AM To: [email protected] Subject: Re: $NULL$ != $NULL$ So any code written for 5.1.2 now may have defects in it that are introduced simply by upgrading. ________________________________ From: Action Request System discussion list(ARSList) [mailto: [EMAIL PROTECTED] On Behalf Of Warren Baltimore Sent: Wednesday, June 13, 2007 4:02 PM To: [email protected] Subject: Re: $NULL$ != $NULL$ ** Nope Norm, I don't think your crazy! I believe your on the money. On 6/13/07, Kaiser Norm E CIV USAF 96 CS/SCCE < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: ** I may be crazy, but I seem to recall from the dark recesses of my mind that when comparing values, if two values are $NULL$, the expression would evaluate to FALSE. That's the way it seemed to work at least up to v5.1.2. For example, suppose I have form A and form B and I do a PUSH FIELDS from A to B if field1on A is equal to field2 on B. As I recall-and I'm pretty certain this is true-if field1 is NULL and field2 is NULL, the PUSH FIELDS qualification fails because it evaluates to FALSE. It seems with version 6.3 (and higher?) this type of expression now evaluates to TRUE??? Am I crazy? __20060125_______________________This posting was submitted with HTML in it___ -- Warren R. Baltimore II Remedy Developer UW Medicine IT Services School of Medicine University of Washington Box 358220 1325 Fourth Ave, Suite 2000 Seattle, WA 98101 The opinions expressed in this e-mail are in no way those of the University of Washington, or the State of Washington. They are my own. __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ -- Warren R. Baltimore II Remedy Developer UW Medicine IT Services School of Medicine University of Washington Box 358220 1325 Fourth Ave, Suite 2000 Seattle, WA 98101 The opinions expressed in this e-mail are in no way those of the University of Washington, or the State of Washington. They are my own. __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
