I was doing some documentation today on this site that is part of a collection of customized sites. It has JavaScript (yuck) and web parts galore. I get to this site that deals with Affiliated Items for this particular site and I notice that there are 5 web parts. I am wondering why do you need 5 web parts when you take in a query string and provide a list of items. What you really only need is a Query String Web Part connected to another Web Part or a Web Part that reads the Query String. For some reason this person is used 3 web parts to do the work and it looks like there are two web parts that are sitting around looking pretty. There are at least 180 instances of this site, so there are 180 places where 5 web parts are residing, instead of the normal one or two and three of these instances on the 180 places are actually doing something of value. Think about the colossal waste of space in SharePoint. We were looking at our backup jobs and noticing how they are at 20.5 gb for the stsadm backups. The SQL Backups are only about 4.5 gb. Something is wrong inside SharePoint in a large way when you are seeing such a major inconsistency. I am going to post in the next week what I do to fix this problem. I will leave you all with a piece of advice. Try to create a solution in as few parts as possible with as much modularity as you can. This kind of programming is what they teach you at school. I'm not saying I am an excellant programmer, but I know there are some precautions that you can take when creating web parts or any type of solutions. Also, another note for you guys please remember to comment as much as possible. Honestly, I would rather see too many comments than too little comments on programs. I am dealing with too little comments on a lot of programs and web parts that I am working with right now. I hope that you all have a nice day and a nice relaxing night.