Abstract: In a database application executing on a computer system, a database table view is represented by a structured object located on a storage device coupled to the computer system. Responsive to a user pasting content (e.g., spreadsheet data) onto the view of the table, the database application determines if the content to be pasted extends beyond the number of rows (records in a database) or columns (database fields) currently displayed in the table view. If the content extends beyond the number of rows or columns currently displayed, the database application automatically adds one or more records or fields to the structured object on the storage device, and updates the table view to display one or more rows or columns corresponding to the records or fields added to the structured object.

Abstract: The disclosed implementations allow automatic and transparent creation of data relationships in a database application or other application in response to user generated trigger events. Related data records can be stored and displayed in layouts, screens, forms and user interfaces provided by the database application or other application. Additional or extended information corresponding to the related data can be stored and displayed.

Abstract: In a database application executing on a computer system, a database table view is represented by a structured object located on a storage device coupled to the computer system. Responsive to a user pasting content (e.g., spreadsheet data) onto the view of the table, the database application determines if the content to be pasted extends beyond the number of rows (records in a database) or columns (database fields) currently displayed in the table view. If the content extends beyond the number of rows or columns currently displayed, the database application automatically adds one or more records or fields to the structured object on the storage device, and updates the table view to display one or more rows or columns corresponding to the records or fields added to the structured object.

Abstract: A compound field is automatically created in response to a trigger event. In one aspect, a user selects a field type and a compound field associated with the field type is automatically created. A compound field can be manipulated and presented as a single conceptual unit in a user interface (e.g., a form, screen or layout) of an application (e.g., a database application). When an object representing the compound field is dragged and dropped or otherwise selected in the user interface, the compound field is expanded to reveal one or more subfields capable of receiving data from a user. In another aspect, one or more background tables are automatically and transparently created to store compound field objects. In another aspect, a user can create their own compound field types.

Abstract: The disclosed implementations allow automatic and transparent creation of data relationships in a database application or other application in response to user generated trigger events. Related data records can be stored and displayed in layouts, screens, forms and user interfaces provided by the database application or other application. Additional or extended information corresponding to the related data can be stored and displayed.