MB Software Solutions General Account wrote: > I was thinking not of the primary table itself but the foreign keys in > other tables. But you're right....I'm probably splitting hairs. Thanks, > Paul!
I could see using tinyint as the foreign key. May even be a great idea for no expense. And if/when you needed to grow it to regular int, you could do that without data loss. And if you are doing tinyint as the foreign key, you may as well do it in the lookup table too. But, as I said, not really worth spinning lots of cycles on. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
