MSDN Article: Building Webparts with the Smartpart: http://www.blogs.jpworks.be/Tom/PermaLink.aspx?guid=30a33a0f-dcda-4d47-9d00-bc0cbe3b5c76

CamlCheck:

http://projectdistributor.net/Releases/Release.aspx?releaseId=89

Thanks Tariq!

I found this on the newsgroups, it's great:

First, you'll want to have installed on your development machine the Microsoft Web Developer Accessories from http://www.microsoft.com/windo­ws/ie/previous/webaccess/webde­vaccess.asp
(though the download page states they're for IE 5.x only, they'll install in IE 5 or higher)

Once they're installed, you'll use them to find the name of the form elements you want to disable.

Browse to your EditForm.htm (for any record) and the right click the page and pick Document Tree...
In the browser window that opens, scroll down to and click OWSForm.
Scroll farther down to where you can see the names of the elements of the form which will look like

urn:schemas-microsoft-com:offi­ce:office#Title
urn:schemas-microsoft-com:offi­ce:office#EventDate
(etc.)

The part after the # should resemble the field name enough to help you identify the ones you need.

Now, in FrontPage, just before the closing </body> tag in HTML view, paste the following <script> code and replace the CAPS stuff as necessary with
your field names (watch for wrapping of the longer lines - they should only break after the ; )

<script language="javascript">
<!--
document.forms('OWSForm').elem­ents('urn:schemas-microsoft-co­m:office:office#
YOURFIELDNAMEHERE').disabled=t­rue;
document.forms('OWSForm').elem­ents('urn:schemas-microsoft-co­m:office:office#
YOUROTHERFIELDNAMEHERE').disab­led=true;
//-->
</script>

One caveat: If the FIRST field on the form is disabled, you'll get an error about not being able to set the focus to it.

Jim Duncan

http://groups-beta.google.com/group/microsoft.public.sharepoint.teamservices.caml/browse_thread/thread/4f8369d2f7e0987e/a14b9d87562e9228?q=OWSMarkup&_done=%2Fgroups%3Fsourceid%3Dnavclient%26ie%3DUTF-8%26rls%3DGGLD,GGLD:2004-11,GGLD:en%26q%3DOWSMarkup%26&_doneTitle=Back+to+Search&&d#a14b9d87562e9228

This post also includes a handy tool for looiking at the sources of web pages:

http://www.microsoft.com/windo­ws/ie/previous/webaccess/webde­vaccess.asp

GotDotNet : SharePoint Query Builder Tool

http://blog.spsclerics.com/archive/2005/01/20/519.aspx

This link is great. A handy tip for seeing how the Portal sends queries is to save one as an alert, then run it again, the Address bar will show how it was constructed.

http://blogs.msdn.com/danielmcpherson/archive/2005/01/18/355342.aspx

This suggestion is one way to do it that people may find useful, thanks Daniel!

http://www.developerland.com/DotNet/Enterprise/253.aspx

"Microsoft Office 2003 is very tightly integrated with SharePoint by utilizing its web services. Windows SharePoint Services comes with sixteen different web services. SharePoint Portal Server 2003 supports an additional five web services. The web services provided by SharePoint do provide a vast array of features. But not all SharePoint features are accessible through them. If required you can build your own web service on top of SharePoint leveraging the managed SharePoint server API itself. The web service interfaces make it very easy to integrate SharePoint capabilities right into your application."

http://msdn.microsoft.com/office/default.aspx?pull=/library/en-us/odc_SP2003_ta/html/Office_SharePointAccessibility.asp

This article describes ways you can customize the site definition files in a deployment of Microsoft Windows SharePoint Services.

http://www.sharepointblogs.com/lishman/archive/2004/12/16/1005.aspx

Here's a useful tip from Marian Lishman's Blog: Which gets around the problem that you can't total a calculated field.