Mcgillivray, Donald [ITS]
donald.a.Mcgillivray at mail.sprint.com
Thu Mar 25 12:39:09 CST 2004
Sounds like this is ground that has been tilled already, but I must have missed the discussion. At the risk of incurring the wrath of the "real" developers on the list, I'm keen to learn the specific objections to the use of this feature. I'm not saying that I use it . . . OK, I DO use it, but I'm not SAYING that. ;o) If there's a thread in the archives that I can browse, I'm happy to seek my answers there (a quick search on "lookup tab" and "table lookup" yielded goose-egg.) Otherwise, I (and perhaps others) would welcome a few "civil comments" on the topic. <ducking and running . . .> Don McG -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins Sent: Thursday, March 25, 2004 10:03 AM 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