ADO ConnectionString TextFile: Difference between revisions

From AutoIt Wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
 
(21 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{WIP}}
Text files accessed via ADO will be read only. ADO does not have a driver that supports writing to or creating text files.
Text files files accessed via ADO will be read only. ADO does not have a driver that supports writing to or creating text files.
=Providers=
==Microsoft ACE OLEDB==
Provider=Microsoft.ACE.OLEDB.12.0
With Office 2010, there are new drivers, the 2010 Office System Driver, which will be provided in both 32-bit and 64-bit versions. You can use these drivers to let your application connect to Access, Excel and text files in a 64 bit environment utilizing the new 64-bit drivers.
 
You don't need to buy or install the Office suite, the components are available as a separate download.
 
==Microsoft Jet OLEDB==
Provider=Microsoft.Jet.OLEDB.4.0


=Arguments=
=Arguments=
The Provider supports the following arguments:
Both providers supports the following arguments:
 
; Data Source=
: Path to the directory where the text file to be processed is stored
 
; Extended Properties="x"
: "x" stands for one or multiple of the following extended properties separated by a semicolon:
 
;: Text
:: Specifies that a text file is to be processed


;FMT
;: FMT=
:This argument tells ADO which delimiter is used for the file. Although the comma is probably the most widely-used delimiter for text files, it's not the only one. Another popular delimiter is the TAB.
:: This argument tells ADO which delimiter is used for the file. Although the comma is probably the most widely-used delimiter for text files, it's not the only one. Another popular delimiter is the TAB.
{| class="wikitable"
:{| class="wikitable"
|-
|-
! Format !! Description !! Schema.ini Syntax !! Connection String Syntax
! Format !! Description !! Schema.ini Syntax !! Connection String Syntax
Line 17: Line 34:
| Custom Delimited || Fields in the file are separated by some character other than a tab or a comma (with one exception: you can't use the double-quote as a delimiter). For example, the asterisk is used as the delimiter || Format=Delimited(*) || FMT=Delimited(*)
| Custom Delimited || Fields in the file are separated by some character other than a tab or a comma (with one exception: you can't use the double-quote as a delimiter). For example, the asterisk is used as the delimiter || Format=Delimited(*) || FMT=Delimited(*)
|-
|-
| Fixed-Length || Fields in a file take up a specific number of characters. If a value is too long, "extra" characters are chopped off the end. If a value is too short, blank spaces are appended to it to make it fill out the requisite number of characters. <br> The columns (fields) of the file need to be defined in a file named Schema.ini. || Format=FixedLength || FMT=FixedLength
| Fixed-Length || Fields in a file take up a specific number of characters. If a value is too long, "extra" characters are chopped off the end. If a value is too short, blank spaces are appended to it to make it fill out the requisite number of characters. <br> The columns (fields) of the file need to be defined in a file named [[ADO_Schema.ini|Schema.ini]]. || Format=FixedLength || FMT=FixedLength
|}
|}


;HDR
;: HDR=
:Specifying HDR=YES means that the test file contains a header row. A header row simply means that the first row in the text file is a list of fields, with all subsequent rows containing the actual data.
:: Specifying HDR=YES means that the text file contains a header row. A header row simply means that the first row in the text file is a list of fields, with all subsequent rows containing the actual data.
[[Category:ADO]]


= Schema.ini=
= External links =
Schema.ini is simply a text file that tells ADO how to deal with your data file(s). This, by the way, is optional only when using a delimited file; if you have a fixed-length text file, you must use a Schema.ini file. In this file, you define the separator to be used (optional) and define the columns (fields) using syntax similar to this:
* [http://www.connectionstrings.com/textfile/ Connection string for text files]
Coln=Fieldname Datatype <additional information>
* [http://msdn.microsoft.com/en-us/library/ms974559.aspx Much ADO about Text Files]
Example:
Col1=FirstName Text Width 7
Col2=LastName Text Width 10
Col3=ID Text Integer 3
After you create the Schema.ini file, make sure you indicate in your script that the file does not use a header row. To do that, just set the HDR parameter to No.


A Separator.ini can hold information for many files. Hence you need to start each definition by the filename enclosed in square brackets e.g.:
[[Category:ADO]]
[File_1.txt]
Format=CSVDelimited
[File_2.txt]
Format=TabDelimited
 
'''Important:''' Schema.ini must be in the same folder as your text file.
 
== Delimiter ==
With a delimited file, this often involves nothing more than telling ADO what the delimiter is:
[MyLog.txt]
Format=TabDelimited
 
== Data Types ==
You can use the following data types:
* Text
* Short
* Long
* Currency
* Single
* Double
* DateTime
* Memo

Latest revision as of 09:44, 10 January 2014

Text files accessed via ADO will be read only. ADO does not have a driver that supports writing to or creating text files.

Providers

Microsoft ACE OLEDB

Provider=Microsoft.ACE.OLEDB.12.0

With Office 2010, there are new drivers, the 2010 Office System Driver, which will be provided in both 32-bit and 64-bit versions. You can use these drivers to let your application connect to Access, Excel and text files in a 64 bit environment utilizing the new 64-bit drivers.

You don't need to buy or install the Office suite, the components are available as a separate download.

Microsoft Jet OLEDB

Provider=Microsoft.Jet.OLEDB.4.0

Arguments

Both providers supports the following arguments:

Data Source=
Path to the directory where the text file to be processed is stored
Extended Properties="x"
"x" stands for one or multiple of the following extended properties separated by a semicolon:
Text
Specifies that a text file is to be processed
FMT=
This argument tells ADO which delimiter is used for the file. Although the comma is probably the most widely-used delimiter for text files, it's not the only one. Another popular delimiter is the TAB.
Format Description Schema.ini Syntax Connection String Syntax
Tab Delimited Fields in the file are separated by tabs Format=TabDelimited FMT=TabDelimited
CSV Delimited Fields in the file are separated by commas (note that there should not be a space between the comma and the start of the next field name or value) Format=CSVDelimited FMT=CSVDelimited
Custom Delimited Fields in the file are separated by some character other than a tab or a comma (with one exception: you can't use the double-quote as a delimiter). For example, the asterisk is used as the delimiter Format=Delimited(*) FMT=Delimited(*)
Fixed-Length Fields in a file take up a specific number of characters. If a value is too long, "extra" characters are chopped off the end. If a value is too short, blank spaces are appended to it to make it fill out the requisite number of characters.
The columns (fields) of the file need to be defined in a file named Schema.ini.		 Format=FixedLength FMT=FixedLength
HDR=
Specifying HDR=YES means that the text file contains a header row. A header row simply means that the first row in the text file is a list of fields, with all subsequent rows containing the actual data.

External links

Retrieved from "https://www.autoitscript.com/w/index.php?title=ADO_ConnectionString_TextFile&oldid=12153"