# Own data adapter ### ![](https://2873353689-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfK1YJaTCqOiS0L22wVKG%2Fuploads%2Fgit-blob-82a409549d31b8d9fc2afc92887e9262c1cd3f24%2FIcon_TOB_data.png?alt=media) You can add your own adapter or copy an existing adapter and fit it to your needs by changing the connect string.

1. On OMrun Ribbon choose `Config` 2. Select tab `Data Adapter`

*** | Column | Description | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | DB Type | Describes what kind of data can be read with this adapter. | | Trusted |

Select checkbox to connect to the data with the credentials of the current user logged-in.
Deselect checkbox to connect to the data with user id and password field provided by Connect String.

| | Provider Group | Displays all the included Data Provider. These information are predefined and can't be changed. If you need an additional data adapter, please get in contact. | | Connect String |

The connect string contains the information that the provider need to know to establish a connection to the database or the data file.

Assembly:
• A connect string consists of a series of keyword - value pairs separated by semicolons (;)

The equal sign (=) connects each keyword and its value
Example: Key1=Value1;Key2=Value2;Key3=Value3;
The information in the connection string is passed on to the provider

The connect string may contains placeholders like myServer, myDataBase and myUserName, myPassword and myPort.
These placeholders will be resolved in Environment.

Click here for more information about connect strings (external link).

| | Remark | Enter your comments or parameter description here. | ### Special Settings

The adapters "Avaloq (Oracle)" and "Avaloq (TNS Oracle)" contain the variable @SessionUnlock which has to be filled in field "Data Source" on screen [Environment](https://gitlab.com/dbiservices/omrun/help/-/blob/v4.x/configuration/customize-own-adapter/element-overview/environment.md%22) as example shown below with the specific command to open the session security for Avaloq systems. *** ### Text Files Options for text files with OLEDB Adapter: Extended Properties="text;HDR=yes;IMEX=1;FMT=Delimited"; Notice that only the directory for the text file is specified in the connection string. The filename of the text file is specified in the T-SQL commands that access data in the text file, similar to a table name in a database. ***

Keyword	Remark
HDR=No	First row does not contain field description.
HDR=Yes	First row contains field description.
FMT=Delimited	Delimited fields with default delimiter. See Windows start button → settings → control panel → regional settings, Number tab → list separator You can access files that use nonstandard text delimiters and fixed-width text files by creating a schema.ini file in the same directory as the text file. A text file, vehicle_semi.txt. A possible schema.ini file for the vehicle_semi.txt file is: [vehicle_semi.txt] Format=Delimited(;) ColNameHeader=True MaxScanRows=0 Character=OEM Col1=VehicleId Long Width 4 Col2=Mark Text Width 255 Col3=Model Text Width 255 Col4=Color Text Width 255 Col5=EmptyWeight Long Width 255
	The connect string contains the information that the provider need to know to establish a connection to the database or the data file. Assembly: A connect string consists of a series of keywords - value pairs separated by semicolons (;) The equal sign (=) connects each keyword and its value Example: Key1=Value1;Key2=Value2;Key3=Value3; The information in the connection string is passed on to the provider The connect string may contains placeholders like myServer, myDataBase and myUserName, myPassword and myPort. These placeholders will be resolved in Environment. Click https://www.connectionstrings.com/ for more information about connect strings (external link).
	Enter your comments or parameter description here. You can specify the fields in the text file in two ways: Include the field names in the first row of the text file and set the ColNameHeader option to True. Identify each column using the format ColN (where N is the one-based column number) and specify the name, width, and data type for each column. The MaxScanRows option indicates how many rows should be scanned to automatically determine column type. A value of 0 indicates that all rows should be scanned. The ColN entries specify the name, width, and data type for each column. This entry is required for fixed-length formats and optional for character-delimited formats. The syntax of the ColN entry is: ColN=columnName dataType [Width n] The parameters in the entry are: columnName The name of the column. If the column name contains spaces, it must be enclosed in double quotation marks. dataType The data type of the column. This value can be Bit, Byte, Currency, DateTime, Double, Long, Memo, Short, Single, or Text. DateTime values must be in one of the following formats: dd-mmm-yy, mm-dd-yy, mmm-dd-yy, yyyy-mm-dd, or yyyy-mmm-dd, where mm is the month number and mmm are the characters specifying the month. Width n The literal value Width followed by the integer value specifying the column width. The Character option specifies the character set; you can set it to either ANSI or OEM.

Format=CSVDelimited	Fields are delimited with commas. This is the default value.
Format=Delimited(customCharacter)	Fields are delimited with a custom character. You can use any single character except the double quotation mark (") as a delimiter.
Format=FixedLength	Fields are fixed length. If the ColumnNameHeader option is True, the first line containing the column names must be comma-delimited.
Format=TabDelimited	Fields are delimited with tabs.

Format=CSVDelimited	Fields are delimited with commas. This is the default value.
Format=Delimited(customCharacter)	Fields are delimited with a custom character. You can use any single character except the double quotation mark (") as a delimiter.
Format=FixedLength	Fields are fixed length. If the ColumnNameHeader option is True, the first line containing the column names must be comma-delimited.
Format=TabDelimited	Fields are delimited with tabs.

Format=CSVDelimited	Fields are delimited with commas. This is the default value.
Format=Delimited(customCharacter)	Fields are delimited with a custom character. You can use any single character except the double quotation mark (") as a delimiter.
Format=FixedLength	Fields are fixed length. If the ColumnNameHeader option is True, the first line containing the column names must be comma-delimited.
Format=TabDelimited	Fields are delimited with tabs.

### Excel Files If column contains a mixed alphabetic and numeric values, use the IMEX setting.: Extended Properties="Excel 12.0;HDR=Yes;IMEX=1"; --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://dbi-services.gitbook.io/omrun-help/version-4.x/configuration/customize-own-adapter/customize-data-adapter.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.