In message <15D4EB38-8600-4B7B-9C5A-30E52D6FC4B1@microsoft.com>,
TomTait747 <TomTait747@discussions.microsoft.com> writes
[quoted text, click to view] >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.
>
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