On Sun, 2 Mar 2008 21:07:03 -0500, "Samuel Neff" <[EMAIL PROTECTED]> wrote: > I would go the ADO.NET route 'cause it'll fit into your .NET application much >better. The overhead is minimal compared to the normal cost of running >database queries (in any database).
The reason I'm concerned about using ADO.Net instead of hitting the SQLite library directly, is that this adds dependencies in addition to the .Net framework. Our customers are anything but computer-savvy, and most don't have anyone technical around in case things don't work, so that I'd like to minimize dependencies as much as possible. Also, what about performance when using the SQLite library directly vs. going through ADO.Net? Hopefully, I'll have VS2005/2008 and SQLite up and running by the end of the week, so I can check for myself. Thank you. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
