SharePoint User Group UK

Hi Laurence There are a bunch of threads here but they are all from some time back. Many are still relevant. To see them, click into the Education forum, then change the Forum Options on the Date filter to 'Show All'. You'll then get to see all the really useful ones from way back. Hope this helps. Regards Alan C.

Helen How did you get on looking at InfoPath?  If you need some working examples of it, and would like a quick walk around the product I'd be happy to provide a web-demo if that would be useful? Regards Alan C.

Helen Sorry about the delay, and I'll add my input for what it's worth. InfoPath will undoubtedly give you the capability you are looking for as you can add conditionality to forms and fields, such that when a field value changes, it recalcs other information and values in other fields etc, You can also add a 'Re-Calc' button and other buttons

Ian I recently attended a SharePoint in the real world session at the Southampton User group, where Dr Jim Milne (of Regs4ships - www.regs4ships.com ) gave an excellent presentation about the horrors of getting data transfer between ship and shore via extremely limited data comms happening.  They provide a very competent SharePoint-based

Aquila Well spotted and I stand corrected!  If a Choice column is used then an SPD WF would not cut the mustard, however in this kind of instance, I personally think having the column as a Lookup makes more sense.  I like using Lookups in preference to Choice fields as they allow for users to make such additions and changes, without ...

I thnk it would be easy to add using a SharePoint Designer workflow as well.  Simply do a check for the value entered in the list and if it isn't there, create an entry with that as a 'lookup' value. Please advise if you would like a little help in doing this. Regards Alan C.

Stu I can envisage at least two different methods that this kind of requirement can be addressed through. Firstly it could be a relatively simple workflow which gets initiated when the document is first created, and that has a 'pause until fields XXX and YYY have been completed' in it. This would act upon the information which the separate ...

Paul Having thought a bit about this one I'd say that the best method would be to use a simple workflow to copy the value from the 'lookup' field into a normal text one.  This allows for the 'new' column to be used in a 'group by' criteria and stops the annoying clickable option.  Creating a workflow of this sort is really easy in ...

Manu / Mark I do agree that Item Level Permissions could potentially give grief if the size of the list is vast, if the machine upon which it is sat is limited and if there are other resource-hungry actions which are happening in the background. And to that end I'd suggest a trial might be a useful thing to undertake to see the potential impact.

Mark Perhaps you wouldn't have to use multiple libraries if you were to use an 'upon creation' and/or an 'upon change' based workflow. This could be configured to identify categorisation columns on the documents and invoke a 'change the permissions' workflow on the document as needed. A simple workflow would then affect the documents ...