Microsoft Access imports and Kathy Nickolaus
..............
On election night, all the people that were to bring in spreadsheets, they were given a spreadsheet template. They were asked not to change that template. When the city of Brookfield results came in on election night,
extra columns were put into that spreadsheet, which would have been a problem if I had tried to import that in. I saved them, but when I imported them into the Access database, I thought that they were saved at that time, and
didn’t have any real reason to believe they weren’t.Here is a spreadsheet with a column heading and 29 fictional votes. The columns are vote number, who the ballot was cast for, and an alternate way of recording the vote: a simple “Yes/No” field for Prosser. Note that rows 23, 24 and 25 all have bad data (“oops”) in what should be a Yes/No column:
Let’s take Nickolaus’ second point first: that when she imported the records she had no reason to think it failed. What happens in Microsoft Access when importing data that has some bad data? How does Access respond when there’s a problem? I created a database with a table called “VoteTable” and tried to import the data I just created in Excel:
Here is what it says about the bad data:
So it throws up
a big warning that explicitly says not all the data was brought in! It also specifies the number of rows that were affected, asks if the user wants to continue, and defaults to No, as in “No - do not import the data.” Nickolaus should have seen a very similar prompt if there was a problem importing her data. (I suspect Microsoft would also have a word or two to say about the allegation that its database product allows imports to silently fail.)
much more (plus spreadsheets):
http://www.pruningshears.us/pruning-shears/2011/4/8/microsoft-access-imports-and-kathy-nickolaus.html