[AccessD] Regarding multi-value field, from a reader

Yeah, those sort of features remind me of junk food.  The worse it is for you, the more folks seem to like to over indulge.  In Excel for example the 'feature' of merged cells is used (and promoted) widely as being a wonderful thing, but can cause you enormous grief and pain if used without due care and consideration.  Of course, no one tells the users that.  They just merge away like buggery.

I can think of many other examples as well...  So much so that I like to use the term (ab)user rather than user with referring to some of my more troublesome employees of my clients.  Hehe.

Cheers
Darryl

-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Thursday, 1 November 2012 2:58 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Regarding multi-value field, from a reader

Trouble is, the users get into trouble with all those little bits that added just for them!

Charlotte

On Wed, Oct 31, 2012 at 8:52 PM, Susan Harkins <ssharkins at gmail.com> wrote:

> Charlotte, that's a fantastic idea! I don't use them either, but 
> they're there for the users.
>
> Susan H.
>
>
>
>  Maybe a little remedial instruction on normalization for the reader?  
> I've
>> always avoided multi-valued fields like plague, but I wonder if you 
>> could fake it by using a hidden column 0 in the listbox with a 
>> numeric sort order and a visible column with the desired values?
>>
>>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/**mailman/listinfo/accessd<http://database
> advisors.com/mailman/listinfo/accessd>
> Website: 
> http://www.databaseadvisors.**com<http://www.databaseadvisors.com>
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com