0

I'm working on a database driven program in Visual Studio 2015, in C#, Windows Form Application, and I'm using SQL Server 2014 for my databases, downloaded the most recent version from the MSDN site.

I've got it working well. But if I want other users on other computers and different versions of Windows, this would require them to have SQL Server installed, correct?

Basically the app is used for storing current medications, moods, a mood quiz, symptoms, etc.. and I store all the results in SQL Server databases. They can be edited, deleted, etc through the program's GUI. Do the users need SQL Server installed to use this app?

If so, is there an alternative to keeping databases without having to have the SQL Server connections, or is there a way to do this without the users having to have SQL Server installed? I don't want remote connections to me, I want it standalone.

Does this make any sense? If not, I can explain more. I know way back in the days of Visual Basic 4 I was making, reading and writing databases without SQL. But that was 16 years ago. So I'm wondering what the easiest solution to this is. Thanks!

sandorfalot
  • 1,042
  • 1
  • 10
  • 19

1 Answers1

1

In other words, you want a database that you can a) distribute to end users freely and b) that will 'connect' just to the copy of the database they have stored locally.

Here are a few options ---

  1. SQLite over ODBC is as-easy-to-use as MSSQL, the driver can be found here:

SQLite ODBC

  1. Use ConfigurationManager.OpenExeConfiguration to read / write your app config .xml file and use it as a key / value store. I can provide examples if needed.

  2. Dynamically create an Access database, it should work as well as MSSQL for most things, with less overhead. Here's how:

Create an Access Database

  1. Use SQLIte DLL. Details on SO

create-sqlite-database-and-table

Community
  • 1
  • 1
JLB
  • 323
  • 3
  • 8
  • Thank you for understanding (you got it right on, I just suck at explaining) and giving me the options. Definitely going to look into them, I'll let you know how this goes. – sandorfalot Mar 20 '16 at 16:16
  • Let me know how it turns out. I can give you working examples of the first three. The interesting thing about the SQLite ODBC driver is that it will let you create an in-memory database as well as a disk-based one, so if you wanted to make your own mini-Redis, you could. – JLB Mar 20 '16 at 22:39