John Bartow
john at winhaven.net
Sat Mar 27 15:54:28 CST 2004
McNo. I don't actually use the lookup property so I don't need the code. I would be s a simple property change so it shouldn't be difficult to do if you really want it though. John -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Ken Ismert Sent: Friday, March 26, 2004 2:33 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Lookup Fields in Table Design McCool. If you have code that does that, I'd love to see it. -Ken -----Original Message----- From: John Bartow [mailto:john at winhaven.net] Sent: Friday, March 26, 2004 12:00 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Lookup Fields in Table Design Here's a stretch but... For people that like to use the added form designing capabilites of the lookup property, once the table design and realtionships are complete you could set the desired lookup properties. Design all of the forms for the application. When the application design is complete you could run code that iterates the table collection and eliminates all lookup properties in the table design. This in essence would eliminate the corruption and performance issues. Eh? -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte Foust Sent: Friday, March 26, 2004 11:39 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Lookup Fields in Table Design There is also the issue of TableID limits, which I believe include all the tables involved as lookups. Charlotte Foust -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com