System.Data.SQLite

I'm glad it worked for you. Sorry, I can't help you on hibernate. You may have to start another thread.

The way to do it is to target the application to run on the x86 processor rather than any cpu. You need to make sure that all the references will also run on 32-bit machines. With that, the O/S will install it so that it runs in 32-bit mode. The manifest will show you if the executable (.exe or .dll) is restricted to run on 32-bit computers. You ...

I had a similar problem. Everything worked fine in the IDE but not when installed. It turned out to be a permissions problem for the folder (I put it in a sub directory of ProgramData). The solution was to grant read, write, execute and list contents priviledges to the folder in the installation package. This was easy in Advanced Installer. I ...

The problem lay in the parameters for the second query. When I changed them from .Add to .AddWithValue all was well. Definitely not a game for a guy who cannot see.

I have two insert routines to insert a record into each of two tables. The date field is typed as "Date." The first insert (new member) works while the second one (record attendance) fails. In fact, the VS2010 designer won't let me put in the date type saying it is not a DBType. It also won't take "yyyy-mm-dd" format ...

I have tried to use drag and drop for a table adapter.  I get the following errors in dataset.designer .vb: Error 2 variable '_connection' conflicts with a member implicitly declared for property 'Connection' in class ...

I downloaded and installed a VS2005 version of C# and could not find an option to target a particular CPU. Have you simply tried to install the app on a 64-bit system? As a minimum, I would use ildasm to disassemble the executable and look at the manifest. Near the bottom of the manifest you should see a line about the type of CPU. If you ...

If you select X86 processor as the target CPU in your compile options then the 64-bit OS will automatically put it in Program Files(X86) instead of Program Files. I routinely do this and have no problem at all.

I executed the following code without problem in Visual Studio 2005: Imports System.Data.SQLitePublic Class Form1 Dim realPath As String = "D:\VisualStudio2005\Projects\DeleteSQLiteDB\StartupDB.s3db"Dim dbConn As SQLiteConnection Private Sub btnEnd_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ...

I've had the same problem. Please look at http://sqlite.phxsoftware.com/forums/p/1473/6393.aspx#6393 for a possible solution.