User Guide : Map Connectors : Source and Target Map Connectors : Clarion
 
Share this page             
Clarion
Clarion is a database application that has its own proprietary format. With the Clarion connector, Map Editor reads and writes Clarion versions 2.1 and 3.0.
You can connect to TopSpeed databases with ODBC 3.x. For details, see the SoftVelocity Web site.
Note:  Map Editor cannot read encrypted or password-protected Clarion data files. The files must be unencrypted and have the security removed before connecting with Map Editor.
See the special note about Clarion dates under Source Schemas.
Connector-Specific Notes
Clarion stores dates as integers. To convert these integers to a more common date format, such as mm/dd/yyyy, after you select your target connector and target file, you need to write an expression for each date field at the Map tab. The expression you write may look similar to the following example:
DateAdd("d", Fields("FIELDNAME"), DateValue("12/28/1800"))
where FIELDNAME is the source field name in the Clarion source data file. The remainder of the expression should be written exactly as shown.
Limitations
The limitations are:
Field Names - Each field name must be unique. Field names may contain up to 10 characters, but the first character must be a letter.
Encrypted Passwords - Map Designer cannot read encrypted or password-protected Clarion data files. The files must be unencrypted and have the security removed before connecting with Map Designer.
Property Options
 
Property
ST
Description
IgnoreMemoErr
S
This option determines how Clarion memo files are handled. Choose you selection from the list that appears. The following options are available:
Never – Default. This option causes Map Designer to always look for and include any memo file fields when the source data file is read.
Errors – Selecting this option causes Map Designer to look for and include any memo file fields when a memo file is present. If present, the memo fields are included with the transformed data. If the memo file is not in the same directory as the data file, the memo file is ignored. This means that the memo fields cannot be included with the transformed data.
Always – Selecting this option causes Map Designer to always ignore the memo file completely. This means that the memo fields cannot be included with the transformed data.
CodePage
ST
The code page translation table tells Map Designer which encoding to use for reading and writing data. The default is ANSI, which is the standard in the US. The following code pages are available:
ANSI
OEM
0037 US(EBCDIC)
0273 Germany(EBCDIC)
0277 Norway(EBCDIC)
0278 Sweden(EBCDIC)
0280 Italy(EBCDIC)
0284 Spain (EBCDIC)
0285 UK(EBCDIC)
0297 France (EBCDIC)
0437 MSDOS United States
0500 Belgium(EBCDIC)
0850 MSDOS Multilingual (Latin 1)
0860 MSDOS Portuguese
0861 MSDOS Icelandic
0863 MSDOS Canadian French
0865 MSDOS Nordic
1051 Roman-8
Data Type
These are the data types of the fields in your target data table. The following data types are available:
Byte
Date
Decimal
Group
Long
Memo
Picture
Real
Short
String (Default)
Time
Output Modes
If you are writing to a new table (Replace mode), you may use any of the available data types from the list for the Type cell of a field.
If you are appending data to an existing table (Append mode), the data type of each field uses the data type in the selected table by default.
Updating Clarion Data
Although Clarion does not have Update as an Output mode, you can still update your Clarion target file. If you have an ODBC 3.x driver installed, you can select ODBC as the target connector and perform an update. Or, you can put the data into an Access database and use that as a staging table to perform the Update in a second transformation. Next, insert the results into Clarion. The transformation can then be tied together in a project.