Command Line Execution

Run Barcode Director from the command line with these options:

File Options
 

File Option	Comment
-c"file_name"	Project file path.  File name must have a .bdp extension
-e"file_name"	Error log file path name.  If not specified, a Message Box shows error
-r"file_name"	Results file path name.
-f"file_name_or_folder"	The names of one or more input files or folders.  If specified, these names will override the input panel definitions in the project file.

Note:  

• The Last Results file is what you see when you select View the Last XML Results in the Session Manager.

• Wild Cards are not allowed in these file path names.  They will generate errors

• No matter in what order the -f options are listed in the command line, they will be processed in ascending chronological order of the Last Modified file property and lexicographic order of folder names.

User Interface and Processing options
 

Option	User Interface	Execution
-p	Minimized in task bar	Executes once and exits, and does not show the UI.
-uy	Status panel	Loads the project file and other options, but does not execute.  User has to press Start or Monitor.
-ux	Status panel	Executes once, then remains in status panel display, waiting for user action.
-up	Status panel	Executes once and exits, however it displays the status panel while executing
-um	Status panel	Executes, showing the status panel display, then continues in Monitor mode

Command Line Execution Examples

Run the program in the usual UI mode

BarcodeDirector

 

Run the program, then exit, using the last saved project file as input.

BarcodeDirector -p

BarcodeDirector -p -c"project_file.bdp"

 

Same as above, but also specify the error log file to hold the error messages.

BarcodeDirector -p -c"project_file.bdp" -e"bd_err.log"

 

Same as above, but add a Last Results File specify the error log file to hold the error messages.

BarcodeDirector -p -c"project_file.bdp" -e"bd_err.log" -r"bd_rslt.xml"

 

Same as above, but also specify input files and/or folders.  This overrides input files/folders in .bdp file

BarcodeDirector -p -c"project_file.bdp" -r"bd_rslt.xml" -e"bd_err.log" -f"c:\inpfile.tif"  -f"c:\inpfolder"

 

Load the project file and other options, but do not execute; let the user make last minute changes.

BarcodeDirector -uy -c"project_file.bdp" -r"bd_rslt.xml" -e"bd_err.log" -f"c:\inpfile.tif"  -f"c:\inpfolder"

 

Run the program in UI mode,  with a project, log, and results file specified.

BarcodeDirector -up -c"project_file.bdp" -r"bd_rslt.xml" -e"bd_err.log"

 

Same as above,  but using one or more input files to override the project file specs

BarcodeDirector -up -c"project_file.bdp" -r"bd_rslt.xml" -e"bd_err.log" -f"c:\inpfile.tif"

 

Same as above with two input files.  Note that the file order on the command line does not matter.

BarcodeDirector -up -c"project_file.bdp" -r"bd_rslt.xml" -e"bd_err.log" -f"c:\ImgBmpC39.bmp" -f"c:\inpfile.tif"

 

Same as above with an input file and an input folder name.

BarcodeDirector -up -c"project_file.bdp" -r"bd_rslt.xml" -e"bd_err.log" -f"c:\ImgBmpC39.bmp"  -f"c:\inpfolder"

 

Execute once, then stay open on the status panel UI.  This example uses two input files.  

BarcodeDirector -ux -c"project_file.bdp" -r"bd_rslt.xml" -e"bd_err.log" -f"c:\inpfile1.pdf" -f"c:\inpfile2.tif"

 

Execute once, then enter monitor mode, using the specified input folder

BarcodeDirector -um -c"project_file.bdp" -r"bd_rslt.xml" -e"bd_err.log" -f"c:\inpfolder"

 

 

 

---