This is a "repost" continuing where a post left off. The subject has changed. The original post was "bas file does nothing".
I get the following error when executing a package from vb script:
Source: Microsoft Data Transformation Services Flat File Rowset Provider
Description: Incomplete file format information - file cannot be opened.

Darren wrote:
Flat File Rowset Provider is the text file driver, so that is the error
source basically. Sounds like something if wrong in that area, or just missing
information, maybe a record terminator.

Then I wrote:
Darrel, this is not all that surprising. The record terminator is a pipe + a return character that appears as a square in notepad. It translates to chr(10) in visual basic. I can't get bulk copy to recognized it to save my life, which is why I'm trying to make it happen with DTS. MS Access can deal with it. DTS has no problem with the file when I run the local package from within Enterprise manager. Why does it cough when I run it from the VB script? (The vb script was created when I saved the package as visual basic from the DTS wizard.) Also, is there a spot in the code where I can define the record terminator?...I could not find one in the bas that Ent Mgr created.

In message <15D4EB38-8600-4B7B-9C5A-30E52D6FC4B1 (AT) microsoft (DOT) com>,
TomTait747 <TomTait747 (AT) discussions (DOT) microsoft.com> writes

I think the key is "there a spot in the code", if this spot is supposed
to be the Chr(10), then you will need to code it as such, as in

Propert.Value = Chr(10) + "|"

I assume the scripting method just takes the delimiter value and wraps
it in quotes, without checking that the delimiter is indeed a printable
character.



--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

In message <AD8BD6CB-B808-4BDC-B8B5-C6160B9A075E (AT) microsoft (DOT) com>,
TomTait747 <TomTait747 (AT) discussions (DOT) microsoft.com> writes

oConnection.ConnectionProperties("Row Delimiter") = Chr(10)

Have a look where the so called spot is, as that is probably the Chr(10)
incorrectly displayed.




--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

I've been having all of these troubles because when the files were ftp-ed from unix, it was done in binary. So the line delimiter was a line feed only. In windows, it needs to be a carriage return (chr(13)) + a line feed (chr(10)). It should be easier from here on out, although I will have more questions I'm sure.

"Darren Green" wrote:

I misread one of your earlier posts, so to clarify, when saving as VB from
the designer, is you use Cr+Lf or a normal printable character then you will
see something like this-

oConnection.ConnectionProperties("Mode") = 1
oConnection.ConnectionProperties("Row Delimiter") = vbCrLf
oConnection.ConnectionProperties("File Format") = 1

If you use Cr or Lf or another non-printable character it looks like this-

oConnection.ConnectionProperties("Mode") = 1

oConnection.ConnectionProperties("File Format") = 1

Note the missing Row Delimiter line, so just add it back, e.g.

oConnection.ConnectionProperties("Mode") = 1
oConnection.ConnectionProperties("Row Delimiter") = Chr(10)
oConnection.ConnectionProperties("File Format") = 1


--
Darren Green
http://www.sqldts.com

"TomTait747" <TomTait747 (AT) discussions (DOT) microsoft.com> wrote

of these files every half hour. I have basically nothing in SQL Server:
View, Tables, DTS-wizard-created packages, T-SQL, BCP. I assume I need to
schedule some jobs and feed a file path to a DTS package to import the file.
Where should I start?