System.Data.SQLite

SQLite database files are really easy to create.  The rule is, if the file doesn't exist, SQLite will create it.  However, if you want to explicitly create the file beforehand, here's how:

using System;
using System.Data;
using System.Data.Common;
using System.Data.SQLite;
 
namespace test
{
  class Program
  {
    static void Main(string[] args)
    {
      SQLiteConnection.CreateFile("c:\\mydatabasefile.db3");
    }
  }
}

The filename can be anything you like and the extension is irrelevent.

What command-line parameters are you passing to sqlite3.exe and what commands are you calling once it starts?

Robert

CreateFile() just creates a blank empty file ... there's nothing in the file for the command-line utility to query on.  Is there any reason you need to run the command-line utility on an empty database?  The command-line utility can create databases on its own as well...

Robert

I'll see if there's a way I can force sqlite to write the master page when creating a file.

Robert

... it's a file, so just use System.IO.File.Delete() to delete it.

Robert

No difference.  Some people just couldn't wrap their brains around the idea that the SQLite engine would create the file for you automatically if it didn't exist on the first call to SQLiteConnection.Open()

Robert

I have never used nor even heard of a Pocket C# compiler ... why would you want to compile on the device?

Ok I looked up Pocket C#.  It doesn't support .NET CF 2.0, which this SQLite data provider requires.

Robert

Sorry, I didn't think about that. Thank you!

I have the source code for PocketC#. So I guess I could try and compile it for use with CF 2.0??

The reason I prefer to compile on the device, is that the family computer might be used by others and I like sitting outside or in a comfy chair (the laptop has a bad power connection - repaired once, so I prefer to leave it in one place).