On what to write the interface to a DB?

Question

SQL

I'll start a little from afar.
Friends keep auto parts stores, the store is already 10 years old, and all the time they work with Excel - it has its own price list, and several files are connected to this price list for generating orders, for printing labels and other garbage. Everything is macro.
But it so happened that the volume of the price list began to exceed 20,000 positions, and all this begins to dull and grind.
For the sake of interest, I raised the 2008r2 MSSQL server, loaded it there, and ran the main queries (replace macros) flies, and the functionality is wider, and, in principle, more cheerful.
Now, with the idea to switch to sql, the question arose - what to write the interface on? Software or web. And what are the real options?
While I was looking briefly, I saw the first convenient one - this is an asp with tied authorization in AD. But somehow I'm not sure about the web solution.

Answer 1

The options are very different, the limit is only in the imagination. You can write a GUI on anything.
I would advise you to formulate the requirements more specifically, and guided by them, it will become clearer on what and how to write.
Sample questions on the requirements:
- where to store the database: locally on a computer or still on some central server?
- Do you need simultaneous access to it for several people / devices?
- Do you really need autonomy and the ability to work without a network?
...etc.
As a result, if you need a base that will be used by many people and you don’t need autonomy, then it’s better to throw it on the server and make a web-face, if you need a simple wrapper around the base locally on one computer for one person and the Internet to a light bulb (ala that the excel file itself is on steroids), then you can generally use microsoft access, or build a GUI in almost any language with a nice (to use) graphical either - C#, Ruby, Python .... thousands of them.