Bishop Alan and the Lambeth Conference

I’ve been quite avidly reading the blog by the Bishop of Buckingham, Alan Wilson, since I came across it a few months back. It’s quite an eclectic mix at times with snapshots from his holidays, pictures of his work around Diocese, and religious comment.

One of the best things about it though is it is quite clearly Bishop Alan – and totally unencumbered by any sort of Diocesan Communications filter – very much like meeting him in person or hearing one of his sermons. Perhaps that might get him in to trouble at some point – but still it is refreshing to find a Bishop being clear and direct, a good example being his post today answering the question as to whether he is going to the Lambeth Conference. Probably the clearest example of this is his third point:

But what about the Windsor report and Lambeth 1:10? Well, this kitchen is full of pots and kettles. I don’t believe in gay weddings, but have I worked as hard as Lambeth 1:10 asked, to listen to and understand gay people’s experience? Honestly, I doubt it. Has the Episcopal Church complied with the Windsor/primates process? They seem to have tried, a damn sight harder than brothers who have ordained other provinces’ dissidents as bishops, lying directly in the face of the Windsor/ primates plan. Why should I be a hypocrite and apply a double standard? All this proves is what I knew all along, that I am as big a sinner as my brother, and we all need grace, and we all need to talk. That’s an argument for coming together, not walking apart.

There was a definite sharp intake of breath having read that one – whilst I certainly agree with the comments on the Windsor process, especially the way the Episcopal Church keeps having bits of the Windsor report quoted at them by people totally ignoring what the same report required them to do, it is refreshing to find a Bishop willing to actually make the point as clearly as this!

Dave Walker has also been inspired to do a cartoon based on another part of the posting.

A SQLServer 2005 Gotcha

We’ve just come up against a bit of a gotcha with Microsoft SQLServer 2005.

We’ve been working on a bespoke system for a customer for the past few months, and have been regularly testing against their test databases that they have been sending over, and they’ve been doing the same. Today the system was set up against their live database for the first time, at which point we got an “Ambiguous column name” error being generated whenever they loaded one of their custom query configurations into our system.

This not surprisingly had us flummoxed for a long while, and it wasn’t until I found this blog post that I nailed down what the problem actually is – SQL Server compatibility modes.

The test database that we have been using was originally created on SQL Server 2000, so when it is attached in SQL Server 2005 the system automatically sets the compatibility mode to 80 – the code for SQL Server 2000. Their live database however has recently been recreated in SQL Server 2005, so when that is attached the compatibility mode defaults to SQL Server 2005, and SQL Server 2005 is a lot more picky about certain bits of SQL syntax. As a result their custom query that works fine on the test system, that reuses a particular column twice and sorts by the same column falls foul of the new syntax rules.

Obviously you can get around the problem by switching the compatibility mode back on the new database, but longer term we’ll need to fix the problem.

It’s not the only change between SQL Server 2000 and SQL Server 2005 either – there is a pretty extensive list of all the changes with a probable impact on this blog post.

Churchwardens Anonymous

So yesterday I found myself in the Church hall in Shinfield, with about fifty other people – a variety of ages and backgrounds. One by one we stood up and introduced ourselves – “I’m Richard from St James’, Finchampstead, and I am a Churchwardenâ€?…

It was the annual Churchwarden training day laid on by the Diocese. Led by the Archdeacon, with the main speakers being the Diocesan Registrar and the secretary of the Diocesan Advisory Committee (the DAC are the people who give us permission to do physical work on the Church – and tell us off when we do work we’re not supposed to!) this was a chance to let all the new Churchwardens known what they should and shouldn’t be doing!

The first problem of the day was actually finding somewhere to park. Like many villages parking is a bit limited. Apparently these training days usually only attract about twenty-five people, but with the Churchwardens Measure now in place providing a number of new people, plus the increasing complications of health and safety rules about double the usual number had booked. We managed to all park along the lane through the middle of the village, but I guess the locals must have wondered what was going on at 9am on a Saturday morning!

The first part of the meeting was a talk by John Rees our Diocesan Registrar. This was particularly interesting as alongside being our registrar, he is also a pretty senior lawyer in the Church, so has been heavily involved in the recent cases such as the ongoing case involving Tom Ambrose in Trumpington. Needless to say he couldn’t comment on the case directly, but he did stress the importance of the Churchwardens in making sure that situations don’t get so intrenched that the only way out is by going to the courts. He stressed in particular the dual roles of the Churchwardens as the chief representatives of the laity, and also as the officers of the Bishop in the parish. Other interesting snippets that came up were also that as Churchwardens we needed to be aware of what else our position might land us in. For example he has currently been dealing with situations where a village school had closed and as the Churchwardens of the local parish Church were named as trustees on the original trust deed the local authority had passed responsibility for the buildings back to them.

The talk by the Diocesan Advisory Committee followed, telling us a variety of anecdotes about what she’d seen. She was well aware that to most people in the Church DAC approval is seen as a real hassle, but she was keen to highlight that her remit was more worship focused and that in her opinion if we had to deal with local authorities things would be much worse. She also said at times she was there to save people from themselves. The example she used was a Church where the daughter of the Churchwarden was getting married. Since the Church was looking a bit drab, they went to the local hardware store and bought some paint to tidy things up. Needless to say they just did it, and although the Church looked very nice for the wedding a few years later the walls were being stripped and dried out because the conventional paint that had been used had been totally unsuitable and the building had sucked moisture into the walls, resulting in a much more expensive problem to solve.

After coffee we had about an hour of questions and discussion. Chief topics of discussion were how to handle the clergy – inspired somewhat by the comments of the registrar earlier on no doubt. There was also discussion about the process of picking a new priest for a parish, particularly the tension as a Churchwarden of wanting to get anybody if you’ve had a long vacancy, but at the same time wanting to get the right person. The most important bit of advice at this point was from the Archdeacon saying that you can refuse everybody as the parish representative. He highlighted one parish that hit problems with a new priest where one of the representatives admitted to not being happy with the choice on the day, but to not having said anything at the time because he didn’t want to make a fuss!

Perhaps the most major topic of conversation was health and safety, particularly the smoking signs, and more important the effects of the Fire Safety Order 2005. Although there were one or two Churches like St James who were lucky enough to have specialists in the congregation who could help, many were struggling. Luckily there is a fellow Churchwarden in the Diocese who has said she is happy to help out with the all important report that the order requires to be produced. One interesting comment came from John Rees who said that despite what the actual order might say, the authorities had said – in some cases in writing – that they were continuing to treat Churches differently. The example he gave is one which has caused problems for us – our 1590 door is too narrow to be a fire exit, and opens the wrong way. However it is the only door at that end of the church so has to be the exit. The rules require that it should open outwards, but being grade one listed we wouldn’t be allowed to re-hang it to open outwards, nor would we be allowed to put another fire exit in place. Under the letter of the law we should therefore limit our occupancy to a maximum of sixty people… John Rees commented that it would very much depend on the use of the building, and that our primary aim should be to satisfy our insurers as to the safety and mitigate any risks as best we could. Although obviously it would be better if we could meet the requirements, for those of us with ancient and protected buildings it does seem to imply that we can go on using them.

All in all it was a worthwhile way to spend a morning – gives you a chance to meet the variety of other people doing the job around the area, and also realise that we all have much the same problems wherever we are!

Clergy Advised to Remove Their Dog Collars

Perhaps the most shocking quote of this BBC article about clergy safety is this one:

One vicar, from Willesden, north-west London, said his vicarage had been machine-gunned – but still did not believe he had experienced violence.

Someone machine-gunned the vicarage!!! More surprisingly is that even after that he doesn’t consider that he has experienced violence…