Visit Boris website Export to Access 2003

Export to an Access 2003 database sends all of the data captured on a form into Access database tables.

The unique names defined for documents and for individual items are used to generate and update these tables - one Access table is created for each document with a name that is the unique name of the document. A field is created within the table for each individual item - the field name is the unique name of the item. Additionally, fields are created within the Access database for the customer, location, date etc and further tables are created to hold values for general purpose lists, customers, locations, templates etc.

Each template outputs to only one database, although more than one template can output to the same database.

Main

Main screen for this action
*Description

A descriptive text to identify this action

*Access database location and filename By default the Access database updated by this action will be created under the filename entered here, in a sub-folder of the root folder. If preferred, a pathname can also be specified so that it is saved elsewhere and this could be a UNC path, allowing you to update an Access database on the network.  The folder does not have to exist already as Boris will create the directory if necessary.  Whilst Report processing variables should work here, they are inappropriate.  Please note that the Access filename must end in .mdb or it will not be recognised by the operating system.

Examples include:
  • MyAccessDatabase.mdb
  • Access_dbs/MyAccessDatabase.mdb
  • C:/Access_dbs/MyAccessDatabase.mdb
Use text of list entries rather than list entry id (useful if you have many different list items) By default Boris will output its own internal ‘id’ for a given list item, together with an Access database table containing the “text” corresponding to this id. In general it is best to do this as it avoids duplication of data.

However, as table sizes are restricted in Access (and for simplicity's sake) it may be necessary to use the text corresponding to a list entry instead.  If so then you can enable this option.

Conditions

This action will only be triggered if the conditions below are met. Leave blank if it is always to be executed.

Condition (1) If you wish to only run an action in a particular situation then you can use these conditions to specify them. The action will only occur if both conditions are satisfied. Typical uses are to only run an action if a particular answer has been given to one of the answers on the template. See Concepts-Conditions
Condition (2) If you wish to only run an action in a particular situation then you can use these conditions to specify them. The action will only occur if both conditions are satisfied. Typical uses are to only run an action if a particular answer has been given to one of the answers on the template. See Concepts-Conditions

Post-action processing (advanced)

After an action has finished running a file can be executed on the server. This could be, for instance, a .exe or a .bat file. Typically this would be used to insert data into another system.

File name to run Enter the full path and filename here.  Ensure that it is correctly spelt and that the file extension (such as .exe or .bat) is also correct.
Command line to run If the file specified above requires additional information on its command line, please enter it here. Contact your Boris expert for further help.
Folder to run from Enter the full path and folder name that the executable programme needs to be launched from.
URL Instead of running an executable file locally, an http request can be sent to the URL specified here. It can contain standard variables.
HTTP verb Choose the http verb to be sent with the request to the URL specified above.  If you do not know what this is, ask your Boris expert.
HTTP request body This will be very different in different circumstances and probably needs to defined at the implementation stage. It can contain standard variables and may contain the data entered on the form.
See Also

Templates

 

 


Parts copyright 2014 Boris Software Ltd. Parts copyright 2014 Firetronic Software Ltd. Parts copyright 1998-2014 Cadence Computing Ltd. All Rights Reserved.

Menus, prompts, fields and options are from a typical installation - some items may not appear as shown. Please contact Boris support for information on additional features.