[AccessD] Report filter property

[Stuart McLachlan]

#'s work OK if dates are always in mm/dd/yyyy. If your users may use different date formats, 
it can cause big problems.


On 12 Aug 2021 at 7:50, Rocky Smolin wrote:

> I always used # on dates in any SQL statement.Habit.  Why try without,
> possibly generate an error and then have to correct it? Delimiting a
> date with the #, AFAIK, will not cause a problem.
> 
> r
> 
> On Thu, Aug 12, 2021 at 5:37 AM Bill Benson <bensonforums at gmail.com>
> wrote:
> 
> > Did that sample leave out bookending dates as
> >      & "#" & Ctl.itemdata(varitem) & "#"
> >
> > Or have I been adding them unnecessarily for my entire career??  :-(
> >
> > On Wed, Aug 11, 2021 at 9:49 AM Martin <martinreid at gmail.com> wrote:
> >
> > > http://www.baldyweb.com/multiselect.htm
> > >
> > > Martin
> > >
> > > On Wed, 11 Aug 2021, 14:31 Arthur Fuller,
> > > <fuller.artful at gmail.com>
> > wrote:
> > >
> > > > I want to pass an In() clause to a report. Can I use the filter
> > property
> > > to
> > > > do this?  The port was originally  written to accept  one
> > > > parameter. I
> > > want
> > > > to remove  and use the In() instead
> > > > What  is the syntax? I have a multi-select  listbox that builds
> > > > on a
> > > dialog
> > > > that builds the In() clause for me.
> > > > --