Import using schema.ini file

[D.Stone]

Related to my earlier post about importing tab-delimited data to
a .adp (Access project), I found a reference which asserts that you
can't use import specifications with a .adp (as I found) but must use
a schema.ini file.

I've only found sketchy details of this file's spec, but when I've
tried it, there's no evidence that the Import wizard is using it. I
have put the schema.ini in the same folder as the text file to be
imported and the contents are as follows:

[mytextfile.txt]
ColNameHeader = False
CharacterSet = ANSI
Format = TabDelimited
Col1=MyCol1 Char Width 2....., etc.

However, the error I get suggests that the wizard is looking in the
first row for column names, and that tab is not being recognised as
the field delimiter.

Is it necessary to tell TransferText somehow to use schema.ini, or
should it look for it by default?

Cheers,

Dave

 

[D.Stone]

Related to my earlier post about importing tab-delimited data to
a .adp (Access project), I found a reference which asserts that you
can't use import specifications with a .adp (as I found) but must use
a schema.ini file.

I've only found sketchy details of this file's spec, but when I've
tried it, there's no evidence that the Import wizard is using it. I
have put the schema.ini in the same folder as the text file to be
imported and the contents are as follows:

[mytextfile.txt]
ColNameHeader = False
CharacterSet = ANSI
Format = TabDelimited
Col1=MyCol1 Char Width 2....., etc.

However, the error I get suggests that the wizard is looking in the
first row for column names, and that tab is not being recognised as
the field delimiter.

Is it necessary to tell TransferText somehow to use schema.ini, or
should it look for it by default?

Cheers,

Dave

FYI, I gave up trying to import the data with Access: using DTS in SQL
Server proved to be a breeze.

Cheers,

Dave