Relationships
Choose a customer by name while storing its key; edit related detail records as a group.
A form generated directly from a table may be technically correct and still be difficult or unsafe to use. Real data entry often spans related records, calculated defaults, validation rules, permissions, and a complete save operation.
PHPRunner and ASPRunner.NET can generate the starting pages, but useful forms come from modeling the user’s task rather than placing one input beside every column.
Design each form around one business transaction. Show the information needed to make that transaction correctly, collect related details together, provide safe defaults, validate both individual fields and the complete record, and save dependent changes as one reliable operation.
An order-entry form is not merely an order table. The user may need customer status, available products, current pricing, delivery rules, line items, totals, and approval limits. List the decisions and required context before choosing which fields appear.
Choose a customer by name while storing its key; edit related detail records as a group.
Derive dates, owners, statuses, and other predictable values instead of asking users to type them.
Limit choices to valid values and explain a failed rule in business language.
Immediate browser feedback helps users correct a field quickly, but server-side validation must make the final decision because requests can be changed or submitted concurrently. Rules that protect data integrity should also be enforced in the database when other systems can write to the same tables.
Both products create add, edit, and view pages from existing SQL databases and recognize common relationships. Page Designer, validation settings, dependent controls, master-detail pages, and events let developers reshape those pages into task-specific forms and coordinate multi-record operations.