http://hristopavlov.wordpress.com/2009/01/19/understanding-sharepoint-sprequest

http://blogs.msdn.com/sharepoint/archive/2008/05/12/posters-for-sharepoint-stsadm-command-line-parameters-now-available.aspx

My company has setup a Sharepoint WSS demo server with some of the applications-templates (CRM, HelpDesk, Credit Management, Procurement)

URL :         http://62.149.225.30/

UserName:    SERVERDEDICATO\SpDemoVisitor

Password:    Decatec

I'm looking forward to your feedback !!

Other Demos

http://blogs.technet.com/john_westworth/archive/2007/09/30/more-sharepoint-demo-goodness.aspx
http://blogs.msdn.com/philoj/archive/2007/09/28/infopath-sharepoint.aspx

Decatec announces Sharepoint Procurement template (beta)

See it on our Sharepoint Demo Server

URL :         http://62.149.225.30/

UserName:    SERVERDEDICATO\SpDemoVisitor

Password:    Decatec

My employer has recently created a Sharepoint 2007 CRM on WSS-MOSS.

Here is the translated page for the Sharepoint 2007 WSS CRM features.

Post on Sharepoint 2007 WSS + CRM

See it on our Sharepoint Demo Server

URL :         http://62.149.225.30/

UserName:    SERVERDEDICATO\SpDemoVisitor

Password:    Decatec

For an enterprise grade CRM, Dynamics Microsoft CRM is more appropriate

I'm in love with BDC, the universal data connector of MOSS 2007. Almost any datasource can be registered in Sharepoint and pretty much used as a "native" List. That's fine and dany as long as one uses pre-existing datasources.

What if would like to use BDC to generate tables to a new datasource like SQL Server?

Well, one can sort of extract the Lists to Access 2007 and then upgrade to SQL Server, but then some datatypes are lost in the transition. If there is one thing MOSS 2007 misses is the the possibility to "use" BDC to generate/map to a new table to a new DB. Lets' say a way to save/map a List in Sharepoint to a new table in SQL Server 2005. Sometimes the Sharepoint storage engine is perhaps too much, or metadata is not used, so that a simple SQL Server 2005 table would be more appropriate. Sometimes, like in my case, I'd want the storage engine to be SQL Server and Sharepoint to be the UI/Web Interface, to keep my data/relational model intact but without losing the special "columns" datatypes of MOSS.

My employer has recently create a HelpDesk entirely build on Sharepoint 2007 - WSS 3.0.

Here is the translated page for the Sharepoint 2007 WSS Helpdesk features.

See it on our Sharepoint Demo Server

URL :         http://62.149.225.30/

UserName:    SERVERDEDICATO\SpDemoVisitor

Password:    Decatec