I've been at this for a couple of days ladies and gentlemen and I can't figure it out. I have an application where I open a connection to a SQLite DB and select some data out of a table. The connection opens fine. As soon as I attempt to read the data via an SQLiteDataAdapter or an SQLiteCommand object using ExecuteReader, my code appears to just stop executing as if it reached the last statement. There are no exceptions, nothing in the EventViewer, etc. It just acts like it reached the end of the code and the program is idle.

I found [this article](http://social.msdn.microsoft.com/Forums/vstudio/en-US/1350c0ac-7e83-41cc-8df8-11318e3c28ee/code-stops-executing-at-dataadapterfill-line?forum=csharpgeneral) that is pretty much the same behavior I'm experiencing.

Some brief info on what I've done:

* I've installed the SQLite 32bit and 64bit binaries.
* I tried setting my CPU type to x86 while using the 32bit SQLite binaries
* I tried setting my CPU type to x64 while using the 64bit SQLite binaries
* I tried using adapter.Fill(), code just stops
* I tried using command.ExecuteReader(), code just stops
* If I don't open the connection before ExecuteReader(), it bombs, indicating the connection isn't open so it at least is able to communicate and know what SQLite is, right?

My code:

```
SQLiteConnection connection = new SQLiteConnection
    ("Data Source=" + srcFile + ";Version=3;New=False;Compress=True;");
SQLiteCommand command = new SQLiteCommand();
SQLiteDataReader reader = null;

command.Connection = connection;
command.CommandType = CommandType.Text;
command.CommandText = "select * from stuff";

try
{
    connection.Open();
    reader = command.ExecuteReader();  //<-- CODE APPEARS TO BREAK OUT OF EXECUTION

    while (reader.Read())
    {
        // Do stuff...
    }

    // Close/Dispose of Connection
}
catch (Exception ex)
{
    // Log error...
    // Close/Dispose of Connection
}

```

Like I said, the code just stops executing right when command.ExecuteReader() is executed or when I was doing the adapter.Fill()...the program is still running, just no more code execution so the reader.Read() is never reached.