From: Joe on 20 Apr 2010 05:12 Al, Karl, John - I really appreciate your input into my question. I now have a couple of options to trial - I'll post back if any problems. Many thanks again guys. -- Joe "John W. Vinson" wrote: > On Mon, 19 Apr 2010 23:10:15 -0400, "Al Campagna" <newsgroups(a)comcast.net> > wrote: > > >Karl, > > I had in mind two colums in cbo1... > > Injury SubInjury > > > > AfterUpdate... is cbo1.Column(1) = Null then... > > > > OnCurrent... is cbo1.Column(1) = Null then... > > One correction: Nothing - not even another NULL - is ever equal to NULL. These > comparisons will fail regardless of what's in Column(1). The correct syntax is > > If IsNull(cbo1.Column(1)) Then... > > -- > > John W. Vinson [MVP] > . >
From: Al Campagna on 20 Apr 2010 10:22 John, That was just aircode... It was just an interpretation/representation of the logic. Please... I would never actually code it like that... Al "John W. Vinson" <jvinson(a)STOP_SPAM.WysardOfInfo.com> wrote in message news:mcdqs5dd6d9us0omt20gmkfvf4f6g2avhh(a)4ax.com... > On Mon, 19 Apr 2010 23:10:15 -0400, "Al Campagna" <newsgroups(a)comcast.net> > wrote: > >>Karl, >> I had in mind two colums in cbo1... >> Injury SubInjury >> >> AfterUpdate... is cbo1.Column(1) = Null then... >> >> OnCurrent... is cbo1.Column(1) = Null then... > > One correction: Nothing - not even another NULL - is ever equal to NULL. > These > comparisons will fail regardless of what's in Column(1). The correct > syntax is > > If IsNull(cbo1.Column(1)) Then... > > -- > > John W. Vinson [MVP]
From: John W. Vinson on 20 Apr 2010 11:44
On Tue, 20 Apr 2010 10:22:48 -0400, "Al Campagna" <newsgroups(a)comcast.net> wrote: >John, > That was just aircode... > It was just an interpretation/representation of the logic. > Please... I would never actually code it like that... > Al I didn't think so... just wanted to warn the lurkers! "Even Jove nods..." -- John W. Vinson [MVP] |