Thank you for such a brilliant download service. Sarah, USA. We hope you enjoy our download service as much as we do. Thanks for your support. To create more accurate search results for Pendragon 5. Simplifying your search should return more download results. Many downloads like Pendragon 5. If this is the case it is usually found in the full download archive itself. Our downloads database is updated daily to provide the latest download releases on offer.
To celebrate our launch we are offering unlimited full download access for FREE! This is a limited offer and will soon expire and revert back to the normal member price. On the device, selecting an option in Field 3 determines which Lookup List will be displayed in field 6. Selecting Gold in Field Displays all the records in the Reference form that have a Reward level of Gold.
Tapping in the City field brings up a list of Cities in the selected State. Tapping in the Company Name field displays a list of companies in the selected State and City. Three special fields and two Reference forms are required to do a Double Cascading Lookup. One field is used to lookup a State. This field is just a regular Lookup List with a list of all the states. The second field, City, does a single Cascading Lookup to look up the cities for the selected State.
The third field, Company Name, does a Double Cascading Lookup to look up all the companies that match the two criteria of City and State. The Reference Form needs a separate field for each criteria that you want to select. Note that to copy fields into the form that is doing the lookup, the field names and field types have to match between the two forms. A Text field can also copy into a Lookup List field. The names of the fields on this form have to match the names of the fields on the form doing the lookup in order for data to copy from this reference form to the form doing the lookup.
Now take a look at the form that is doing the Double Cascading Lookup. This form has the 3 fields needed to do the Double Cascading Lookup. Field 1 is called State and is just a Lookup List field referencing a Lookup List called States with a list of states. Field 2 is called City, and is a Lookup List field that instead of referencing a Lookup List, references the first Reference form which is called States and Cities.
Still in Field 2, on the Script tab is the script that selects all the cities that match the state from field 1. Field 3 of the form doing the lookup is the field that does the Double Cascading Lookup. Next look at the Script tab of this field. The also statement combines two select statements. The second select statement acts on the records already selected by the first select statement. A Custom Main Menu is a form that acts as a Main Menu and replaces the standard Pendragon Forms main menu screen that shows the list of form designs.
When a form begins with the word MENU, the form is launched as soon as the user launches Pendragon Forms, so that the mobile user does not see a list of form designs, they just see the contents of the MENU form. Only one record is created for the MENU form. Only one form on the mobile device can start with the word MENU in uppercase.
Typically, Custom Main Menu Forms feature Button fields or Section fields typically with pictures that are used to direct the user to different forms. To start, create a new form whose name begins with the word MENU in uppercase letters. You can add a picture to a Section field.
Add a new record to a form. Review existing records for the form. Optionally, the ability to delete records from the mobile device. Synchronize the mobile device. In case of a problem with the Custom Main Menu form, include a way to access the standard Pendragon Forms main menu screen. You will need to create a separate Section field or Button field to serve as the menu option for each of these activities.
A click: event script in each field allows each activity to be performed. Each of these menu options is described on the pages that follow. A click: event script in the Button field allows users to add a new customer record. The gotosubform "formname" new statement jumps the user to the specified form, and creates a new record for that form. The following script is in field 1 of the form shown below the 'Add a New Customer' menu option : click: gotosubform "Customer Info" new This means that when the user taps in the Add a Customer button, the script will go to the form named "Customer Info" and create a new record.
After creating the Custom Main Menu form, remember to create all the other forms that the Custom Main Menu form refers to in each script. Tip: In this example, the contents of the MENU form that the mobile user needs to access all fit on one screen.
An open: event is used as it will run every time the mobile user opens the MENU form. The script is: open: disable nextbutton. To create a menu option for reviewing existing records of a form: The select all "formname" statement selects all the records of the specified form. The review "formname" statement lets the user review the selected records for the specified form. The following script is in Field 2 of the form shown below the Select an Existing Customer menu option : click: select all "Customer Info" review "Customer Info" This means that when the user taps the Select an Existing Customer button, the script will select all the records in the form named "Customer Info" and display a Review screen.
The user can tap on a record on the Review screen to go to that record. If you are using a Custom Main Menu form, you will need to provide mobile users a way to synchronize their data. In the example below, a Button field called Synchronize is created to allow users to synchronize the mobile device. The script in the Button field to start synchronization is: click: synchronize. With a Custom Main Menu form, the mobile user has no way to access the standard Pendragon Forms main menu screen that shows the list of forms.
It is strongly recommended that you add to your Custom Main Menu form a way to access the Pendragon Forms main menu. In the event that there is a problem on the mobile device, you can direct the user to revert to the Pendragon Forms main menu to troubleshoot things like verifying how many form designs are on the device, or verifying what the form ID numbers are.
However, to access the Pendragon Forms main menu, the Next button first needs to be made visible so that the user can go to the second screen. A Button field named Admin is added to the form, and when the mobile user taps the Admin button, the Next button at the bottom of the screen is displayed.
The script in the Admin button is: click: enable nextbutton On the second screen of the MENU Form, a Text field is used to store a password, and a Button field is used to validate the password. The user reverts to the standard Pendragon Forms main menu. If the password is not correct, a message is displayed. If you have set up an administrative password to access the standard Pendragon Forms Main Menu, then entering the password and tapping the button to unlock the Custom Main Menu form will end the Custom Main Menu form and revert to the standard Pendragon Forms Main Menu that shows the list of forms on the mobile device.
Button fields and subforms can be used to create a custom menu option that allows the mobile user to jump to a form and then once in that form, have the choice of reviewing existing records or creating new records.
If a subform is being used, then the Custom Main Menu form will act as the parent form, and the rules governing parent forms and subforms will apply. In particular: In order to link the parent form to the subform, the two forms must have at least one field in common - that is, the same field name and field type - within the first 10 fields of the form.
The common field can be hidden on both parent and subform. The linking field must be filled in on the parent form in order to automatically copy down to the subform. One way to achieve this is to set a Default Value in the field on the parent form.
In the picture below, Field 1, called Form Reference, is going to be used as the linking field between parent and subform. The field is a Numeric field that is made hidden, and a value is pre-populated by setting a Default Value of 1.
A Button field is added to the custom menu form to allow the mobile user to jump to each subform. The scripting statement gotosubform "formname" normal jumps the user to the specified subform. In the picture below, the script in Field 2 is: click: gotosubform "Customer Contacts" normal This script takes the user to a subform called Customer Contacts.
Notes on the Custom Main Menu form: If all the buttons that the mobile user needs can fit on one screen, then: The End button and the Previous button can be hidden by setting the appropriate Advanced Form Properties for the form. If the mobile user only needs to see the first screen of the Custom Main Menu form, you can use a script to hide the Next button as well. The open: script in Field 1 is: open: disable nextbutton If you needed to show the Next button on some screens and not on others, you could instead use enterscreen: events to disable nextbutton or to enable nextbutton.
On the subforms that you create for the Custom Main Menu form, you must add at least one field that the subform has in common with the parent form. The linking field must have the same field name and field type as on the parent form, and must occur within the first 10 fields of the subform. In the Subform A picture below, the field that is used to link with the parent form is Field 1, called Form Reference, which is made hidden. Field 1 of a form is typically used for displaying records when reviewing a form, but since Field 1 is hidden in this case, a different field on the form is set as the Display key field.
In this instance, Field 2, Company Name is set as the Display key field. In the Subform B picture below, the linking field between parent and subform is not the first field on the subform. Subform A Subform B On the mobile device, the user can tap a button to jump to the subform of their choice.
The user can tap the New button to add a new record or tap on an existing record to review that record. Tapping the End button on the subform returns the user to the subform review screen, and tapping Done on the review screen returns the user to the Custom Main Menu form.
If records of a form are pre-loaded onto the mobile device, a Custom Main Menu form can be set up as a way to filter the records.
That is, the Custom Main Menu form acts as a place to enter selection criteria. The review statement preserves any select statement filters that have been set by a script. The also statement is used to combine select statements. In the form below, Field 1 stores a Zip code, and Field 2 stores a Maximum Price that a potential customer wants to pay for a house. Field 3 is a Button field with a click: event that lets the user view records based on the criteria set up in Fields 1 and 2.
The first select statement in the script selects all records in "House Listing 1" that match the zip code entered on the Custom Main Menu form. The also statement saves the currently selected records, and applies the next select statement on top of the existing selected records. The review statement then displays the selected records, that is, all records within a certain Zip code and where the seller's asking price is less than the buyer's maximum price. On the mobile device, when the user enters a Zip code and a maximum buyer's price and then taps the Section field to perform a search, a list of available houses that meet the criteria are displayed.
The user can tap on a record to select it and view details. This causes there to be one record per user. Depending on the application that you are trying to build, you may need more than one form on the handheld to implement your solution. Pendragon Forms supports the following: Parent and Subform A parent form and a subform or child form are used if you need to be able to create many child records for every parent record.
Visiting the same customer or patient more than once, or taking several readings from the same piece of equipment may require you to create a parent form for the information that stays constant e. Lookup to Another Form If you want to maintain a reference list, such as inventory item numbers and prices, or employee names and addresses, and you want to select from the list and copy the data into a form, then you need to maintain two forms and do a Lookup to Another Form.
Creating an application to allow mobile users to take customer orders is an example that requires multiple forms. Step 2 Publish Distribute forms to every member of your team with the click of a button. Step 3 Capture Collect data in the field thanks to Pendragon's offline capabilities. Advanced solution development. Morbi euismod ex vel facilisis. Design Forms on your Desktop and Distribute to Mobile Devices Pendragon Forms is a robust forms designer and mobile data collection software.
No coding required. Easily Manage View your data online or export it for an in-depth, offline analysis. Secure Data Sync your data from anywhere online to a secure cloud database. Advanced Solutions Create sophisticated apps using barcoding, geo-location, scripting, and other advanced features. Enterprise Integration Easily integrate your custom solution into your existing IT ecosystem.
0コメント