DWUTKA at marlow.com
DWUTKA at marlow.com
Fri Mar 26 14:46:04 CST 2004
Hit below the belt. Charlotte, back to your corner! LOL Actually, I think I'd rather be known as the Crusador of the Self Taughts. I like to challenge the 'bad practice' stuff a lot, because I have found that a lot (certainly not all) is based solely on developer limitations, not actually system limitations. If you look at the sides I have been on, I am rarely saying people MUST do something, but instead, they CAN do something, if they choose to. Like the bound/unbound debate. I was simply pointing out that there is nothing wrong with an unbound form. There are times where it is easier to use an unbound form. There are also times where it is easier to use a bound form. But saying that unbound forms are bad practice, or a waste of time, is not right (it doesn't apply to bound forms either). Also, like the original thread, Frameworks are handy. They aren't good for every situation, but they certainly can be useful in other situations. JC has done a superb job of bring light to the subject, and has written excellent code examples. I must admit I don't prefix my Class objects, and variables the same way, but if JC gave me code, and said it will do what it's supposed to, I would have absolute faith that it would. If JC needed me to write code for him, and said, 'hey, use my naming convention, and work within my framework', I would have no problem doing so. Then again, if JC said 'Drew, develop this, but don't use API's because their vauge and mysterious, and don't use indexing, because it'll bloat the database and it's just a lazy way for developers to speed up their applications, instead, roll your own indexing', I'd look at him like he was nuts! (Not picking on ya JC....LOL) Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte Foust Sent: Friday, March 26, 2004 1:26 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Lookup Fields in Table Design >>most generally the "bully" of the group's mentality Are you talking about Drew?? <evilgrin> Charlotte Foust -----Original Message----- From: John Bartow [mailto:john at winhaven.net] Sent: Friday, March 26, 2004 10:50 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Lookup Fields in Table Design Charlotte, You'll find that most people are more strongly opinionated than I am (on many issues). While I may jest about starting flame wars, I really don't enjoy seeing people argue. However, I do enjoy seeing people debate an issue. Especially a group with as intelligent and capable people as we have here. There are many lists where one gets chastised for not conforming to the group mentality (most generally the "bully" of the group's mentality)- I don't stick around those lists very long - not because I can't take getting chastised but because there is really not much one can learn from people who think they have all of the answers for all eternity! And there is certainly little opportunity for me to "help" anyone in that situation. I do try to give back what I can on any list I am on (including directing people to this list). I question the status quo. I listen to all sides of an issue (and there are usually more than two sides). I make a decision. I recommend things based on informed decisions. I accept that not everyone is going to take my recommendations. I revisit my decisions on a regular basis to see if there are compelling reasons to change them. I believe this is why I am a very good "consultant". John PS: We'll just leave my capabilities as a "programmer" out of it! ;o) -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte Foust Sent: Friday, March 26, 2004 12:19 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Lookup Fields in Table Design John, You are NOT getting into the spirit of this discussion. Reasonableness has no place here! <VBG> Charlotte Foust -----Original Message----- From: John Bartow [mailto:john at winhaven.net] Sent: Friday, March 26, 2004 10:00 AM 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 -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com