In SQL Server 2005 you can get a list of all your Tables with a particular name using the system table sys.table:

but if you need to do the same task in a SQL Server 2000, you should use

because sys.table is not supported into SQL 2000.

A common problem in SharePoint 2007 is when you need to delete a Content Type from a List or from a Document Library: you receive the error 'The Content type is in use'. Ok, you understand that there is still a List or a Document Library that is using it and even if you remove all the associations from all your lists if you try to delete it you could receive again the same error.... 'The Content type is in use'
What's going on?
If you look at the msdn you will read that:

A content type cannot be deleted from a list if that list contains items of that content type.

So the problem is that you still have items in your List that are associated to that Content Type. A fast workaround is to select all the items, send them to the site's recycle bin, remove the Content Type and finally restore all those items from the bin back to the List.

msdn reference: http://msdn.microsoft.com/en-us/library/bb802962.aspx

A common task during SharePoint's developing is to read from a SharePoint List a item's (SPListItem) value defined in column. It's not a big deal if you information is stored into a text field:

This is an easy and fast approch that works well if your column (SPField) is defined as text (SPFieldText), but what happens if you try to read from a different column type, such as from a LookUp Field? What you will get is a rappresentation of that value with this syntax:  ID;#TITLE .

Whould it be much better to obtain directly the referenced SPListItem, so you can do whatever you need? Learn how efficently read values from SPFields from this code snippet which is focused to read from lookup fields, but this kind of implementation can be applied on every SPField type:

So remember that when you need to read values from SpListItems, first check your SPField's type,  the cast it and then obtain the value you need.

In this post you will learn how to implement a Picker Tree Dialog into your custom SharePoint 2007's pages and handle the postbacks generated when and user press the OK or the Cancel button. Searching on the web i've found differents implementations, but none of them cares about postbacks that are generated once you submit the form.
If you didn't recognize what is a SharePoint's Picker Tree Dialog, look at this image:

This control comes only if yopu are using SharePoint's Moss (standard and enterprise) versions and is not avaible in Windows SharePoint Services (WSS). It allows you to browse the entire SiteCollection and to select Sites, Lists and Document Libraries. Now you will learn how to retreive the selected items on server side using postbacks.

I will show how to use this control into a SharePoint's custom Page that is located under the /_layouts/ directory, but it won't be complicated to implement this tecnique into a SharePoint's WebPart. Let's start....

First you need to import a directive for SharePoint's dll into the ASPX markup page:

and then add a reference to the PickerTreeDialog.js:

As you see you can see, I use a localized PickerTreeDialog, so it doesn't matter if your web site is in english or in a different culture.
Next you need to add 2 javascript funcions that will care on showing up the Picker Tree Dialog and handling the Postbacks caused from pressing the OK button.
Add this 2 JavaScript functions:

The performPostBack() funcion will perform the Page's postback and launchPicker() function will pop up the control.
To invoke the launchPicker() function, let's use a classic Asp.Net Button control:

Now we need to implement the IPostBackEventHandler interface into the page's code Behind, to be able to capture postback's paramters from server side.

Use the interface:

and implement the required method:

Now, everytime the Ok button is pressed your PickerParameterParser() method will be invoked and the param[]  array will contain all the PickerTreeDialog parameters that are passed using the callback.

Lets's see what happens everytime you select a different item from the Picker Tree Dialog:

The Root site has been selected:

param[0] = Area:?Type:Guid:
param[1] = SiteRelativeUrl

example:

param[0] = Area:?SPWeb:33cc66fc-c251-47a1-984a-3bb7e751a6cb:
param[1] = /

A sub site has been selected:

param[0] = Type:Guid:
param[1] = SiteRelativeUrl

example:

param[0] = SPWeb:fd00f025-b7df-4eae-83c0-7aec11c9929c:
param[1] = /YourSubSiteName

A List has been selected:

param[0] = Type:Guid:ParentType:ParentGuid
param[1] = SiteRelativeUrl
param[2] = ListName

example:

param[0] = SPList:a525db03-551b-44c4-9450-e7add15e510c?SPWeb:33cc66fc-c251-47a1-984a-3bb7e751a6cb:
param[1] = /
param[2] = YourListName

It's not hard to understand that a possibile PickerParameterParser implementation could be something like:

Have fun...

If you want to install or remove SharePoint's WebParts on runtime using SharePoint's object model, you need first of all get a reference to the page's SPLimitedWebPartManager. This reference can be easy obtained through the SPWeb object, invoking the GetLimitedWebPartManager() method. Here's a code snippet:

Once you got your SPLimitedWebPartManager you can add or remove your WebParts by calling the AddWebPart or DeleteWebPart methods.
Imagine that you have installed in the farm a custom WebPart and now you need to insert it or delete it from a SharePoint's page. Let's says that your WebPart is named MyWebPart and  declared as:

The code snippets that you need to use for accomplishing this task are:

Adding a WebPart

Removing a WebPart

Have fun...