[AccessD] Framework Discussion - set up question

Oh, you mean the field property setting that then makes any controls based
on that field have the lookup table/query fields preset to be a combo, list
box, etc.?

What the heck, I'll throw it out there, I haven't seen a debate on this one
yet :o)

I though it was a pretty hokey "feature" at first. IIRC correctly R:Base did
this for you automatically if you placed a combo on a form that had a
primary/foreign key relationship. In other words it actually used the entity
relationships to do it for you.

I don't generally use it but about the only thing I can think of hand is
that it is not dynamic (in A97-I've never even looked into in A2k+).

I did use this once in a situation (A97) where I had to allow for local user
customization and I didn't trust any of the local users to have a clue
beyond the card game. I figured they would get as far as opening datasheets
and never figure out how to create forms so I set a lookup for every
primary/foreign key relationship just because it would force the datasheets
to display the values rather than the autonumberIDs. I had a few break on me
there which is why I don't generally use them.

What else in wrong with it?

John "lighting fires" B.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Susan Harkins
Sent: Thursday, March 25, 2004 12:03 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Framework Discussion - set up question


No. :) I'm talking about the built-in lookup field feature that lets you
display a related value from another table. Open a table in Design view and
click the Lookup tab in the Properties pane.

Developers soundly trash them, but I find them rather cool -- and if abused,
is that Access's fault? ;) I'm mostly in favor of anything that makes Access
more available to the average user -- it IS a desktop application after all.


No, I don't use them, and I often have to "undo" them in Northwind when I'm
using that db in an article example, but I can see why users would like and
use them.

Here we goooooooooooooooooooo! ;)

Susan H.

Susan,
I've seen people joke about this before and I've just assumed I knew what
they were referring to ("hard coded" delimited lists that are not stored in
a table).

Is this a correct assumption?


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