VB.NET读取SQLite数据库失败：Conn.Open后代码未执行直接加载窗体

Hey there! Since you've got solid coding experience but are new to .NET, let's break down why your SQLite code is stopping right after conn.Open() and how to fix it. This is a common pitfall when starting with .NET database operations, so let's tackle it step by step.

1. Catch Hidden Exceptions (Most Likely Culprit) #

The biggest reason code "disappears" after a database call is an unhandled exception that's silently terminating your code block. In WinForms/WPF, unhandled exceptions in the form load event can sometimes skip the rest of your code without showing an error message.

Wrap your database logic in a try-catch block to expose what's going wrong:

private void Form_Load(object sender, EventArgs e)
{
    try
    {
        // 使用using语句自动释放连接资源，避免泄漏
        using (var conn = new SQLiteConnection(@"Data Source=YourDatabase.db;Version=3;"))
        {
            conn.Open();
            // 这里放你的数据读取和文本框填充代码
            var query = "SELECT Column1, Column2 FROM YourTable LIMIT 1";
            using (var cmd = new SQLiteCommand(query, conn))
            {
                using (var reader = cmd.ExecuteReader())
                {
                    if (reader.Read())
                    {
                        textBox1.Text = reader["Column1"].ToString();
                        textBox2.Text = reader["Column2"].ToString();
                    }
                }
            }
        }
    }
    catch (Exception ex)
    {
        // 弹出错误信息，帮你定位问题
        MessageBox.Show($"Error occurred:\n{ex.Message}\n\nStack Trace:\n{ex.StackTrace}");
    }
}

This will immediately show you if there's a problem like a bad connection string, missing database file, or permission issue.

2. Verify Your SQLite Connection String #

SQLite connection strings have easy-to-miss details that can cause Open() to fail silently (or throw an uncaught error):

• File Path: Use an absolute path (e.g., @"Data Source=C:\Projects\YourApp\YourDatabase.db;Version=3;") or ensure the database file is in your app's executable directory. If using a relative path, double-check the working directory of your app in debug mode.
• Permissions: Make sure your app has read/write access to the database file. If it's in a protected folder (like Program Files), you might get a permission error.
• Correct Provider: Ensure you're using the right SQLite library (e.g., System.Data.SQLite or Microsoft.Data.Sqlite)—the connection string syntax can vary slightly between them.

3. Check for Thread/Async Issues #

If you're experimenting with async database calls, missing the async modifier on your form load event can cause unexpected behavior. For example:

// 错误写法：没有async修饰符，await会导致代码异常
private void Form_Load(object sender, EventArgs e)
{
    var conn = new SQLiteConnection(...);
    await conn.OpenAsync(); // 这里会编译错误或运行时异常
}

// 正确写法
private async void Form_Load(object sender, EventArgs e)
{
    try
    {
        using (var conn = new SQLiteConnection(...))
        {
            await conn.OpenAsync();
            // 异步读取数据...
        }
    }
    catch (Exception ex)
    {
        MessageBox.Show(ex.Message);
    }
}

Since you mentioned using conn.Open() (the synchronous method), this might not be your issue, but it's worth double-checking if you've mixed sync/async code by accident.

4. Double-Check Debugger Breakpoints #

You said you confirmed the code skips after conn.Open(), but just to be thorough:

• Ensure your breakpoints on lines after conn.Open() are enabled (not grayed out).
• Check if your debug session is in "Release" mode instead of "Debug"—some optimizations can make breakpoints behave unexpectedly.

Start with the try-catch block first—it's the fastest way to get to the root of the problem. Once you see the error message, fixing it will be straightforward!

内容的提问来源于stack exchange，提问作者The Special