[AccessD] reporting and multi-value fields

You guys think too much like developers and not enough like users. :) I'm
not opposed to the setup. But, I do think they should provide a built-in
way to parse for querying and reporting.

Susan H.

On Sun, Dec 7, 2014 at 1:38 PM, Arthur Fuller <fuller.artful at gmail.com>
wrote:

> Susan,
>
> Stuart has it 100% correct, IMO. Multi-valued columns violate everything
> we've learned from Codd and Date and others.
>
> A suggestion for an article by you, Susan. Find out why the Access dev-team
> decided to add this abomination. That would provide most interesting
> reading. What were they drinking when they came up with this most asinine
> notion?
>
> On Sun, Dec 7, 2014 at 9:20 AM, Susan Harkins <ssharkins at gmail.com> wrote:
>
> > Right Stuart. I was wondering about the best way to parse the elements.
> Any
> > thoughts?
> >
> > Susan H.
> >
> >
> > >
> > > Second best - you need to separate them out in the underlying query,
> put
> > a
> > > report grouping
> > > on the primary record's key and put the rest of your information in the
> > > section header with
> > > only the MV values in the detail section
> > >
> > >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
>
>
>
> --
> Arthur
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>