Archive for July, 2009

CNN’s anti-Christian Bias?

Tuesday, July 7th, 2009

Codex SinaiticusJust read an article on CNN (“Oldest known Bible goes online“) about the online unveiling of the Codex Sinaiticus. This particular article is misleading as to the particulars of the difference between the ancient codex and modern Bibles, and demonstrates a complete lack of understanding on the subject (or significant anti-Christian bias) by its author.

To have apocryphal books present in an ancient codex is not unusual, nor unexpected; most of the books mentioned indeed are still present in Bibles that you can buy from the bookstore. They aren’t missing, they aren’t seditionary — but it seems the article is trumped up to make excitement that everything you thought you knew about the Bible isn’t true!

The discussion about changes and corrections in the codex does not include any thought as to whether the changes were corrections towards the accepted text or deviations from it; the part about missing passages doesn’t bother to mention whether the omissions are due to missing pages or damage or were never written.

There is also no discussion of the possible theological bent of the monastery where this was copied, which could have led the scribes to change it for their purposes (see the Jefferson Bible, for instance).

I don’t expect a news reporter to spout the standard Christian doctrine, but I do expect a discussion that respects and represents the nuance of the subject in question. And the fact that they would never write an article like this about the Koran reinforces the possibility that this is, plain and simple, anti-Christian bias.

Bad journalism, bad scholarship, and patently offensive besides.┬áCNN, you’ve done it again!

Access 2007 Debugging Disabled?

Thursday, July 2nd, 2009

So I was trying to debug a rather convoluted report-generating VBA module in Access 2007 (code which I did not write, but which I have inherited for pro-bono support). But no matter what I tried, Access would not stop for debugging breakpoints.

I did my normal Google searches to see if this was an issue, and I was finding nada on the subject, until I came across this lovely little post.

Turns out there’s a little setting in the Current Database options screen called “Use Special Access Keys.” The little help icon seems to indicate that this setting controls whether or not the special key combinations to bring up the database window, etc., will be enabled (you might disable this normally for end-users using an Access app, for instance). But what it fails to mention is that this setting also controls whether or not the debugger is active!

Check the box, close and re-open the database, and voila, breakpoints. Now I have to go back and remove all those message boxes that I was using when I couldn’t get debugging to work…