Database Connection Commands

Required Edition

Automation, Enterprise Automation

/UID=<userID>

When using ODBC data sources, the /UID and /PWD can be specified to log into the ODBC databases. The /UID and /PWD are applied to all ODBC databases found. If /UID is provided and /PWD is not, then it is assumed that the /PWD is "". The /UID must be used when /PWD is used.

/PWD=<password>

When using ODBC data sources, the /UID and /PWD can be specified to log into the ODBC databases. The /UID and /PWD are applied to all ODBC databases found. If /PWD is provided the /UID must also be provided.

/RecordRange=<range>

Specifies a range of records to be printed. For example:

/RecordRange=1,3,7-10,50…

When using /RecordRange you must be explicit as to whether or not the file specified by /D contains a header record or not. Use /DbTextHeader to indicate that the new database has a header record.

/D=<path to data file>

Sets or changes the text file database to be used. If no connection to a text file database has been added to the BarTender document, the /D parameter adds it.(BarTender will assume that the first line of the file is a header that contains the field names and that the data fields are delimited with the mixed-quote-and-comma method.) If connections to one or more text file databases have already been added, the file specified with the /D parameter replaces the first text database. (BarTender will assume that the new file uses the same delimitation method as the original file, and it will assume that the first line is a header of field names if and only if the original file had such a header.) The /D parameter applies to all open BarTender documents unless the /AF= parameter has been used. A full path to the database may need to be specified.

For more information, refer to How BarTender Processes Path and File Names.

/DbTextHeader=<number of record containing field names>

Indicates that the text file database specified by /D contains a header.

/?<query prompt name>="<query prompt value>"

Assigns a value to the specified query prompt. If there is no match, then the command is ignored. If a query prompt within the document is not set, then the query prompt dialog will be displayed with the remainder of the unset prompts. Multiple query prompts are supported on the command line. Setting query prompts only takes effect when /P, /PD, /FP, or /FPD are specified.

/DD

Causes the deletion of the ASCII data file after the print job if there are one or more databases and the first database is an ASCII database.

/W="<where clause>"

Sets the where clause for record selection within an ODBC database. The where clause will be applied at the time of data browsing or at the time of printing to perform record filtering. The /W option uses the Custom SQL option. If you do not already have a custom SQL statement defined, then one will be generated automatically. The custom SQL statement is parsed for the first occurrence of the WHERE string in your custom SQL statement, and will replace all remaining text with the contents of the <where clause>. If a WHERE clause is not found in your custom SQL statement, then the <where clause> value will be placed at the end of your SQL statement.

The /W parameter is obsolete, and is supported only for backward compatibility. Use the /?<query prompt name> option as an alternative.

/IDOC="<path and file name of IDoc>"

Specifies the IDoc file to be used. A full path to the file may need to be specified. For more information, refer to How BarTender Processes Path and File Names.

/DIDOC

Causes deletion of the IDoc file following the print job if the first database is an IDoc.

/ITD=\path\<SAP definition file name>

Specifies the SAP definition file to be used. This changes a registry entry so that subsequent runs of BarTender will use this file. A full path to the file may need to be specified. For more information, refer to How BarTender Processes Path and File Names.

Related Topics