Home/ Questions/Q 8832231
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T08:28:54+00:00

I wrote an application in c# & SQLite for storing data of all employees

  • 0

I wrote an application in c# & SQLite for storing data of all employees in a company which has around 500 employees. I want to put the database & the application in a file server/shared folder (MS server). Then all employees will have a shortcut of the application in their desktops. I want to make some input fields (text box) enabled/disabled based on the permission of the user runs the application. Whats the best practice for doing that?

I want the user can read/write in the database through my application only (the application is located in the same database folder). I don’t want the user to reach the database without my application. How to do that?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t want the user to reach the database without my application

    If your application will directly access the SQLite database via a Windows file share, this is impossible. Sure, you can make it inconvenient, but it’s not really possible.

    The only way to achieve this really is by introducing some middleware.

    This would typically be a service (WCF perhaps) that listens for connections from your client application, authenticates them, and manages all access to the underlying database. The database would be stored in a location that is visible to the server only, and not visible through a Windows share to your users.

    Also, SQLite isn’t exactly a great choice for a multi-user system. You can kill two birds with one stone here – switch to a DBMS (MS SQL Server Express is free, also MySQL, PostgreSQL are common free choices) that accepts client connections over a network, and build your application to connect directly to the database server (using integrated Windows authentication may also be possible like this, so you can avoid an explicit logon). In a simple scenario this may be adequate and avoid you needing to build an explicit service layer.

    In a more complex scenario, it can still make sense to have a middleware layer between the application and the database – this way, you can change the database design without changing the application design and deploying to all of your client machines – instead, just change the middleware layer in one place and your application won’t know the difference.

    • 0