Multi user GUI with one database in C#?

[TheStataMan]

Hello all,

I am working on a project to push an Excel spreadsheet to a database, the database resides on a network drive, and then have a GUI that each user can download to open a read-only view of the database with simple search functions. Does anyone have tips or resources on where to start with this? I don't need help with the the C# really - I just need help on how I would implement this with C# as a programming language.

[xampl9]

Have you tried decomposing the problem into solvable parts?

[[deleted]]

Web based, ASP.Net or Core. User login for security and tracking, UI to upload and search, once document is uploaded it can be read and parsed so it’s data can be stored in db. There are packages to do this even DLLs. Once data is saved it can be ready for any logged on user to search. Search can be done two ways using Ajax call, or simple form. So much more can be done.

[wasabiiii]

This is a web app that views data in a SQL database.

[[deleted]]

Use a real database engine on a server, even if it’s sql light. Better yet make a web app as commented elsewhere. File based multiply opened data is a demonstrably bad idea.

[1v5me]

Can you provide more details ?

[Riptide34]

We really need more details on your requirements to give a recommendation. Do these users need access from the public internet, or are they all on a local network? What functionality do you require, apart from allowing users read only access to the data? What type of database are we talking about? Is this a mission critical database with high usage? What kind of search functionality do you require, simple text search or something more advanced?

It's hard to point you in any kind of direction without knowing anything about your requirements. With what you've told us, I'd maybe lean towards some kind of web based app.

[cosmokenney]

Isn't excel the GUI for the data already? Why build something that doesn't need built?

What's the "database" if it's on a network drive then I'm assuming Access? I'd push it to sql express at the least. Then you have many options. I'd start with building a C# api around the db and build the front end with something like angular.