John Bartow
john at winhaven.net
Sat Mar 27 15:53:44 CST 2004
+.5 for the sayers! Score: nay-sayers 4 / sayers 8.5 -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Stuart McLachlan Sent: Friday, March 26, 2004 8:26 PM To: Access Developers discussion and problemsolving Subject: RE: [AccessD] Lookup Fields in Table Design On 26 Mar 2004 at 19:35, Ken Ismert wrote: > > >It doesn't affect that, BECAUSE it's a property that is only > >looked at by the Wizards, NOT by Jet, when retrieving the data. > > Its used in queries too. Queries inherit this stuff from the table they are > based on. > Queries don't use it. The object which Access uses to display the results of queries does. If I pull a "Select * from tblMyTable", my recordset doesn't know anything about the combobox bound to fldMyLookup - or about any table used for the lookup on that field. If however, I use the Query Datasheet to display it, the datasheet will look at the table definition to determine how it is displayed by default (which can be overwritten by defining a different display format in the query grid itself). In essence, the lookup property(ies) of a field in a table are no different to the Format, and Caption properties. They are used to define the *default* way that the data in the table is displayed in the GUI. You can overwrite this default in any query grid, form control, report control that you create. It has nothing to do with how a recordset is actually retreived by Jet. -- Lexacorp Ltd http://www.lexacorp.com.pg Information Technology Consultancy, Software Development,System Support. -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com