The following naming conventions allow you to easily determine an item's function:
|List Tables||_list - TableName|
|Background Forms||_background - ViewName|
|Analysis Forms||_analysis - ViewName|
|Dropdown Forms||_dropdown - FunctionName|
|Related Forms||Parent View Title: Related View Name|
The following should be followed when actions are not buttons.
- Maximized - Forms can be maximized in 2 ways.
- Set the form width and height to 100% in the Display panel.
- Use the Alter Form action.
- Native Close Button - Its helpful to hide the Native Close button(s) of your form(s) if there is logic associated with your close action.
- Remove Unneeded Properties - Removing unnecessary fields from a form helps to optimize download time.
- Remove Unneeded Actions - Any unneeded actions should be removed from your forms to optimize loading speed.
- Comments - Commenting individual actions in an action chain allows you to easily determine what each action is doing within the chain.
- Close Action Comment - Should include Name or ID of the form that is being closed. - ex: Close the "Select User" form .
- Automation Actions - Using the default macro icon allows you to easily determine which actions are not called from buttons on a form.
- Troubleshooting - Use message boxes between actions in an action chain to display variables when troubleshooting.
- Clearing Variables - Variables should be cleared ('') once they are no longer needed or the user closes the form.
- Multi-functional Forms
- Using separate variables for background form allows the form to potentially be multi-functional by passing that variable to another form.
- Actions added to a background form can be called from other open forms for added 'hidden' functionality using variables.