条码软件 - SAP
If you can't deal with these limitations, we suggest you to use XML as data import format.
Follow the instructions below to create a hyperlink for HTML or PDF output using variable data (data fields):
Switch to the HTM view (small icon above the input field) and insert the following expession:
<a href='" + LinkHref + "'>" + LinkDisplayName + "</a>
In this example the data field LinkHref contains the URL and the data field LinkDisplayName includes the hyperlink text.
The NVE / SSCC check digit is calculated the same way as UPC/EAN number. Here are the steps:
You have to reconstruct the barcode (EAN and Mod-10) check digit function with the customary functions of TFORMer.
a) Create new data fields: NVE_17 (string) and NVE_Checkdigit (long).
b) As Pre-Evaluation in the detail area, the following check digit extension is the result of:
// first add odd positions from right to left
(index is zero based)
NVE_Checkdigit = CLng (Mid (NVE_17, 16, 1))
+ CLng (Mid (NVE_17, 14, 1))
+ CLng ( Mid (NVE_17, 12, 1))
+ CLng( Mid (NVE_17, 10, 1))
+ CLng( Mid (NVE_17, 8, 1) )
+ CLng(Mid (NVE_17, 6, 1))
+ CLng (Mid (NVE_17, 4, 1) )
+ CLng ( Mid (NVE_17, 2, 1) )
+ CLng ( Mid (NVE_17, 0, 1) )
// multiply with 3
NVE_Checkdigit = NVE_Checkdigit * 3
// sum of digits in even pos
NVE_Checkdigit = NVE_Checkdigit
+ CLng (Mid (NVE_17, 15, 1))
+ CLng (Mid (NVE_17, 13, 1))
+ CLng ( Mid (NVE_17, 11, 1))
+ CLng( Mid (NVE_17, 9, 1))
+ CLng( Mid (NVE_17, 7, 1) )
+ CLng(Mid (NVE_17, 5, 1))
+ CLng (Mid (NVE_17, 3, 1) )
+ CLng ( Mid (NVE_17, 1, 1) )
// at last perform mod 10 with remainder calculation
NVE_Checkdigit = (10 - (NVE_Checkdigit % 10)) % 10
After that, check the NVE-Check digit if the same check digit is in the barcode.
Use the CheckDigits function:
CheckDigits (2, NVE_17)
Currently you have to use a page header area for this tasks. For a future version of TFORMer, a special property which controls this behavior is planned (using this property you can control this behavior in the group header or group footer).
In order to format a date-value properly, TFORMer requires a value of type "Date" (and not of type string).
Solution: Convert your String data field to the type Date with this function: CDate(DateExpiration)
CDate(..) parses the string and extracts the date from it. If this is not possible, it returns the actual date (Now()). The date string must contain the date in the format of the actual system locale (e.g. English: "mm/dd/yyyy" or "yyyy-mm-dd").
It is not possible to load variables defined as "nvarchar(MAX)" into TFORMer. Instead of the real content just empty strings are imported.
nvarchar(MAX) fields can not be imported into TFORMer version 6.0 or below. This will be fixed in a future version.
Workaround: Choose another data type for the table column or cast the data field type to another one in the SQL-Query. Below you can find an example:
Select DATALENGTH(longText), CAST(longtext AS varchar(3)) AS 'longText' from dbo.tblTest
Unless you do not work already with impersonation, the PDF creation always takes place on the web server in context of the calling user. This requires that the calling user have sufficient permissions on directory level at calling time.
These are writing permissions on
Please read this IIS7 Blog article.
For printing through Windows printer drivers, the size of the output medium is always retrieved from the printer driver. For the built-in output formats PostScript, Image, PDF and ZPLII the formats are retrieved from the settings in the TFORMer.xml file.
Declaring a specific paper format directly in the report is not possible, but you can choose from the existing formats through tray selection (see TFORMer Designer manual, tray selection for details).
In TFORMer Designer you have several layout options (e.g. rows=auto or fixed, columns=auto or fixed, height=auto or fixed, etc). In other words, through the report properties it is possible to auto-adjust label/output size to the output media (paper size) or to use fixed values (independent of output medium).
Make sure that both section in the printer driver properties contain the same settings:
The following TFORMer expression converts the German date format 24.12.2009 (contained in data field ProdDate) to US date format 12/24/2009.
Mid ( ProdDate,
Find(ProdDate, ".", 0) + 1,
FindReverse(ProdDate, ".", 0) - Find(ProdDate, ".", 0) - 1 ) + "/"
+ Mid(ProdDate, 0, Find(ProdDate, ".", 0)) + "/"
+ Mid(ProdDate, FindReverse(ProdDate, ".", 0)+1, 4)
If this occurs during printing, this effect is caused by the printer driver (especially with thermo label printers). If this occurs during bitmap generation, this effect is caused by the screen driver.
The solution is to change the drawing-mode of the barcode library. Edit the TFORMer.xml configuration file and change the following entry:
<!-- Settings for TBARCODE lib -->
<!-- drawing-mode Specifies method for drawing bars on gdi printers -->
<!-- 0 = Default -->
<!-- 1 = Compatible -->
<!-- 2 = Advanced -->
<TBARCODE drawing-mode="2" />
Then restart TFORMer (or your TFORMer SDK application).
You may get this error message when you create a new form.
Possible cause: this error message can occur if an incompatible display driver is installed on the computer. Resolution: extend the color-depth from 16 bit to 32 bit or install a driver update.
More infos - see Microsoft Knowledge Base Article - 235618 .
During installation, you may get an error message regarding the IsScript engine like "Cannot find IsScript.msi " or "The version of IsScript.msi is old ".
Please check out the Install Shield Help Page Q108158 regarding this problem.