Search
Let users find a customer or transaction by familiar business identifiers.
A SQL Server database may already contain the right data model, stored procedures, and years of business records. The missing part is often a safe, understandable interface for the people who use that data.
Tools such as ASPRunner.NET can build that application layer without replacing SQL Server, but the important design decision comes first: users should work with business tasks, not database tables.
Keep SQL Server as the system of record. Put a web application in front of it that exposes task-focused pages, validates changes, applies application permissions, and turns related records into complete workflows. Do not give business users a generic table editor and call it an application.
A customer, order, and payment may live in separate tables, but a user thinks in terms of opening an account, approving an order, or resolving an unpaid invoice. Begin with those actions. Each action tells you which records must be shown together, which fields can change, and which checks must run before saving.
Let users find a customer or transaction by familiar business identifiers.
Show only the fields and commands required for the current task.
Validate the complete business action before committing its changes.
The application normally connects with a controlled database account. Individual users sign in to the application, where roles determine which pages, records, fields, and actions they can use. This avoids distributing database credentials and lets permissions follow business responsibilities instead of SQL Server administration roles.
Existing views and stored procedures often encode valuable rules. Reuse them when they represent stable business logic, but do not let their technical shape dictate the page layout. A view can supply a report; a stored procedure can complete an operation; the web application can still present both in language users understand.
ASPRunner.NET connects directly to SQL Server and creates searchable lists, forms, reports, dashboards, authentication, and permissions around the existing schema. Page Designer and application events provide places to reshape the generated pages and add business logic without moving the data into a platform-owned store.