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

Jim Dettman jimdettman at verizon.net
Thu Nov 1 11:36:43 CDT 2012


 It's the overall trend with Access (and sorry for the expression), but they
just keep dumbing it down for the end user.

 The problem with that is their going to loose all the real developers that
work with it and it won't be half as useful as it once was.

Jim.

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

<sigh>

I think you're right. :)

Susan H.


> Because it would confuse the end users.  Scary!
>
> Charlotte
>
> On Thu, Nov 1, 2012 at 7:26 AM, Susan Harkins <ssharkins at gmail.com> wrote:
>
>> Well, what I don't get is this -- Access actually does all the
>> normalization for these fields internally. If they can do that, why not
>> just push it to the interface and do it all the way? Why hide it?
>>
>> Susan H.

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list