First, you shouldn't have to 'think' the problem is somewhere, you need to know where it is - by correctly logging errors and viewing those logs. Don't print stacktraces because you probably won't be able to see them. Instead, use Log.e(...) to log the results so you can view them in LogCat.
Second,
you should read your logs so you can tell if there is something going wrong that isn't crashing the application, but still logs as an error. There will be one (and I bet it is either an IO error preventing you from writing the file or a SQL error because the table you are trying to read doesn't exist).
Finally, you copy and pasted the code from here:
http://www.reigndesign.com/blog/using-your-own-sqlite-database-in-android-applications/. Did you read the comments there? There are two likely problems, both discovered on that code in 2009. One has a simple fix, and the other a not so easy fix.