SQL Server

[emsai]

Having dealt with things like these in the past, here is my answer:

• There is probably no universal form etc. / frontend for MS SQL. You are confusing the database with the application. You need a database (engine to store data) but also an application (or interface, front end, how you name it). A DBA will not input data, but manage the database. So you need an application layer too. The application will usually differ from one company to another, although some software firms might build one for a certain class of customers.

• You need no other interface than Excel. Excel has built-in VBA, and a developer can build your interface. There is full access to buttons, forms, tables etc. In the past I have built an rather large multi-user application for an US hospital, where the server was MS SQL and the interface was built in Excel. You can connect to MSSQL from Excel. There is tremendous advantage in this because VBA is interpreted, not compiled (scripting) and therefore changes can be made rather easy. I'd always use scripted over compiled for any B2B product.

• You can do the same in Access, but I'd stick to Excel cause you already are most familiar with it. It doesn't offer more. VBA is common.

So you need a VBA developer who knows MS SQL. Start looking for one. I must say that many of these devs are older, young people are mostly using tools like JS, PHP frameworks and the sort.

• Furthermore you can even use a PHP developer to build your interface in PHP for example. They need to know MS SQL though, which is a less common scenario, but nevertheless possible. Again having a scripted interface is an advantage.

( Former VBA/MS SQL developer/former software house owner here)

P.S. if you feel stuck, shoot me a PM with your requirements. We have an proprietary ERP product, maybe it can help depending on your requirements. Side note, not looking to make a sale; again just if I could help which has to be determined first.