No, actually, you are right.
I had mis read the requirement. The poster wanted to vaporize the
semi-colon if the field preceding it was null
HS
"Ken Snell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Assuming that Field1 is always to be printed, regardless of its value,
then
> yes.
>
> --
> Ken Snell
> <MS ACCESS MVP>
>
> "HSalim" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > Ken is right about null propagation, but you would use
> > (Field1 ) & ( ";" + Field2 ) & ( ";" + Field3 )
> >
> > HS
> >
> > "Ken Snell" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > Use + as the concatenation operator instead of & between the field and
> the
> > > semicolon:
> > >
> > > (Field1 + ";") & (Field2 + ";") & (Field3 + ";") etc.
> > >
> > > The + propogates the Null and "cancels" out the other character.
> > >
> > > --
> > > Ken Snell
> > > <MS ACCESS MVP>
> > >
> > > "Joanne" <(E-Mail Removed)> wrote in message
> > > news:070301c37d8b$b7b82290$(E-Mail Removed)...
> > > > I am building a report that contains several consecutive
> > > > fields, concatanated and separated by semicolons. Does
> > > > anyone know how to set up the report so that the
> > > > semicolons are not inserted if there is a null value in
> > > > previous field.
> > > > Any help appreciated!
> > > > Joanne
> > >
> > >
> >
> >
>
>
|
Similar Threads
