SharePoint User Group UK

I've been struggling along with an implementation of the fab 40 template.  For getting up and running it's brilliant but has since (i'm sure in my colleagues eyes) turned me into a torrets suffer !  :¬)

Is there a stable solution out there that doesn't let users overbook each other, not break if they edit or delete a reservation ?

In a similar 2003 post there's a link to....

Steven Van de Craen's  unofficial updated version of the template on his blog here http://www.moss2007.be/blogs/vandest/archive/2008/04/21/rooms-and-equipment-reservations-v2-unofficial.aspx .
I've not tried it yet but there are a fair few issues reported on that too.

Has anyone had any good results with any 3rd party solutions or would recommend a system ?

Thanks in advance !
Pete

---

Nothing is as it seems, nor is it otherwise.

hi,

i cant really recommend it as I haven't installed and played with it at all, but Microsofts SharePoint Guidance November release contains an example training course booking application as a "RiverWind" type tutorial about how to do developments in sharepoint.  It may be of use to you - download from http://www.microsoft.com/DOWNLOADS/details.aspx?FamilyID=c3722dba-6ee7-4e0e-82b5-fdaf3c5ec927&displaylang=en

---

Cheers,

Nige

As a method to get a working version of a resource booking system up and running asap, i used a custom list type made by James Finn - http://www.codeproject.com/KB/sharepoint/SharepointReservation.aspx

It seems very good, especially when compared to the MS Template - everything seems to have been working well for about a month now.  There are no overbookings, edit & delete work and you get proper messages if you try and overbook !

The one very minor issue is that for reoccurring bookings, they don't seem to work for bookings spanning multiple days, which isn't really an issue for all but one of our users (therefore it's not an issue at all).

Oh and it means a list for each of your resources, which is a bit different to the MS Template.

Pete

---

Nothing is as it seems, nor is it otherwise.