(94 years since 1914)
Be careful what you type !
Where I work we deal with a lot of companies and use quite a lot of fax transfers. Not many of the companies we deal with have even gone to electronic faxes (like using an electronic fax system like OneBox.Com), and just a very small few use emails ! It's probably because it's all to do with medical matters and that faxes are legal documents.
Anyhow, yesterday a local hospital sent us some information, including a fax number for themselves. Over the next couple of hours our system duly sent out the proper faxes to this fax number, as it should ... however, the fax number was for someone completely different ! Not surprisingly, this gentleman was seriously upset with us, so our call centre received a less-than-polite call from a less-than-happy person.
We blocked our fax output to him within about 15 minutes of being told of the problem, found the cause of the problem about 30 mins later, and rang him back about an hour after he first rang in. Although still not too happy, he was, at least, gracious about the matter. He explained that the same thing had happened a few months before with one of the large companies that do blood testing, and it took him 3 months of yelling to get it fixed ! He was getting psyched up to have to do the same thing with us, but didn't have to.
The moral of the story is to treat incoming information with care and to be responsive to other people's complaints and problems (one day it may be you on the receiving end !).
PS Thanks very much to Sarah (St Bloggie de Riviere) for the poppy.
Here's a little fragment of code for those trying to trap errors in T-SQL before moving to SQL Server 2005:
declare @intError int
-- put the code that could break in here.
SET @Error = @@ERROR
IF(@Error != 0)
-- do what your reaction should be
and here's how to get just the date in T-SQL:
SELECT DATEADD(dd, 0, DATEDIFF(dd, 0, GETDATE()))
That's all for now, folks.