CRUD processing with access controls to SQL Server database

Question

We have built a large database model (SQL Server) for our client and an automated way to load the data into something like 100 database tables. Unfortunately due to time constraints (isn't this always the case?) we need to have some capability to offer the client to have access (CRUD access) to these tables for about 20 users. In addition this access needs to be controlled. We have an app that's already running at the client (web app C#/.NET) and would rather have something "behind" that. In the longer term we would build UI screens, but for now they just need some access to the data.

I have thought of a few ideas but I'm looking for other ideas in terms of software or architecture to achieve this:

1. Use MS Access and have it connect directly to SQL Server and create 20 or so users in the database and set them up with MS Access locally. The cons: They don't like desktops having direct access to these databases and prefer a web solution. Also the 20 users are dispersed and getting this done seems more difficult for them.
2. Same as #1 except use something like DB Visualizer.
3. Find some MS Access or DBVisualizer like control to put behind our login page (we have authentication set up on an internal IIS Server and they prefer to use this)...but does these "controls" actually exist that I can plug in to a C#/.NET app?
4. Using scaffolding generate everything. Haven't done this and I assume this still will take some work and probably be throwaway in the end since the long term goal is building "real" UI pages.

I'm open to any ideas.

Thanks in advance.

Answer 1

ASP.NET Dynamic Data may be exactly what you're looking for. It's a scaffolding solution and would get something basic up and running very quickly. I'd suggest giving it a look.

Additionally, there's a CodePlex release that includes a sample of using Dynamic Data with forms auth. See the section titled "Secure Dynamic Data".