Section - 5 : PDF417 DAL Functions

---

You can also use the following DAL functions to implement a PDF417 solution:

• P417DalCreateNYAAMVAData

• P417DalCreatePDF417Barcode

Registering the functions

Since these DAL functions are not registered by default, you must register them in the INI file. This will look something like this:

Where Keyword left of the equals sign represents the DAL script function name you want to register.

To the right of the equals sign, DLL->FunctionName represents a DLL to load and the exported function name associated with the script function.

Registered in this manner, you can then reference these functions in a DAL script just like any other built-in function. For instance, you could register these functions as shown here:

And then refer to them as CreateNYAAMVAData() and CreatePDF417Barcode() in your DAL scripts.

You could also register the functions as shown here:

And then refer to them as NYAAMVA() and PDF417() in your scripts. How you register these functions is up to you, just make sure the name you use is descriptive.

Both DAL functions work virtually identical to the PDF417 rules.

P417DalCreateNYAAMVAData

Use this function to create the data you want to place in the bar code.

Syntax

Parameters	Description
DALVariableName	Specifies the name for the DAL variable that will contain the 570 bytes of formatted data be stored into a PDF417 bar code by a later call. You can make several calls using this data to create bar codes of different sizes and locations, but which contain the same data. Keep in mind that this function is typically run once, while the CreatePDF417Barcode function can be called several times using the same source DAL data.
RequiredLevel	The New York application defines a number of variable data elements to be included in the bar code. Some of these elements are required. This parameter lets you decide when and to what extent to check for these required data elements. If you enter one (1), if any required fields are missing from the data, an error is issued for each missing field. If you enter two (2), if any required fields are missing from the data, a warning is issued for each missing field. If you enter three (3), processing continues and no errors or warnings are issued if required fields are missing. The default is 3. Other INI options control whether the Rules Processor continues processing or stops on errors and warnings. These options are documented in the Rules Processor System Guide.
INS_Key	Each insurance company that writes auto insurance for drivers in New York will receive a unique key signature. This value is an armored hex string. This parameter specifies that key. If you omit this parameter, you must include this information in the INI file. For security reasons, you may want to have the source code to this rule customized to hardcode the constant key value into the rule. The base version does not provide this option. If you use the INI file to provide the information, specify the value as shown here: < NYAAMVA> Ins_Key = value

This function returns DALERR_SUCCESS if successful. Otherwise, it returns DALERR_USER and shows a dialog.

P417DalCreatePDF417Barcode

Syntax

P417DalCreatePDF417Barcode (DALVariableName, FontID, BarCodeName or BoxName, ECCLevel, TopCoord, BottomCoord, LeftCoord, RightCoord)

Parameter	Description
DALVariableName	Specifies the name for the DAL variable that will contain the 570 bytes of formatted data be stored into a PDF417 bar code by a later call. You can make several calls using this data to create bar codes of different sizes and locations, but which contain the same data. Keep in mind that this function is typically run once, while the CreatePDF417Barcode function can be called several times using the same source DAL data.
FontID	Specifies PDF417 font you want to use for this instance of the bar code. You can choose between two sizes of PDF417 bar code fonts: 9 dots high by 12 dots wide and 12 dots high by 16 dots wide. While Oracle does not mandate the IDs you can use, it does provide an FXR file which contains the attributes for the two fonts. The IDs for these fonts are: 912 and 1216. Note: Prior to release 11.2, the PDF417_2.FXR and PDF417.FXR files were provided to licensed PDF417 customers. In release 11.2, the new REL112.FXR file contains the PDF417 font references found in the two PDF417 FXR files previously included in this product. See for more information on the included FXR files, see PDF417 FXR Files.
BarCodeName (or BoxName)	Specifies a name for the bar code or box. This name can be the name of a box object located on the current section. It is required to provide the root name used by a series of dynamic text labels that contain the bar code text data.
ECCLevel	Specifies the degree of error correction to be used in the bar code. The range is from zero (0) to eight (8). The default is four (4), which is the value recommended by the NYSID. For more information, see Sizing a PDF417 Bar Code.
TopFAPCoord LeftFAPCoord BottomFAPCoord RightFAPCoord	Each bar code instance must specify a location and a rectangular size. There are two ways to specify this information: - from a named box object on the FAP file - from explicit rectangle coordinates The rectangle coordinate parameters are optional. When included, the coordinates explicitly provide the dimensions of the rectangular area to contain the bar code. If you omit the rectangle parameters, the system loads the FAP file for this section and searches for a box named BarCodeName. For optimal performance, specify the rectangle’s coordinates.

This function returns DALERR_SUCCESS if successful. Otherwise, it returns DALERR_USER and shows a dialog.