Results 1 to 3 of 3

Thread: [MSSQL2000] chr(13) problem when export to text files

  1. #1

    Thread Starter
    Fanatic Member
    Join Date
    Sep 2004
    Location
    Jakarta, Indonesia
    Posts
    818

    [MSSQL2000] chr(13) problem when export to text files

    for example a column with "erick [enter] widya" when exported it put 'widya' one row below 'erick' where it need to be in same row so when imported back otherwise it return error

    is there a way?

    my final effort is : using somekind Spesial Character to replace [Enter] whenever it saved into a table so it can fit in one row when exported and when read back just replace those Spesial Character with [Enter]

    but i just need to be sure that there's no other way

    thanks

    1st NF - a table should not contain repeating groups.
    2nd NF - any fields that do not depend fully on the primary key should be moved to another table.
    3rd NF - there should be no dependency between non key fields in same table.
    - E. Petroutsos -


    eRiCk

    A collection of "Laku-abis" Ebook, Permanent Residence

    Access Reserved Words, a Classic Form Bug, Access Limitation, Know run Process and the Lock they hold in, Logging User Activity in MSSQL,
    Kill Database Processes

  2. #2
    Fanatic Member kaffenils's Avatar
    Join Date
    Apr 2004
    Location
    Norway
    Posts
    946

    Re: [MSSQL2000] chr(13) problem when export to text files

    Why not use the REPLACE function in SQL Server. Replace CHAR(10)+CHAR(13) (or was it CHAR(13)+CHAR(10)?) with a space.

  3. #3

    Thread Starter
    Fanatic Member
    Join Date
    Sep 2004
    Location
    Jakarta, Indonesia
    Posts
    818

    Re: [MSSQL2000] chr(13) problem when export to text files

    thanks kaffenils

    Replace CHAR(10)+CHAR(13) (or was it CHAR(13)+CHAR(10)?)
    i think the 2nd one is correct Carriage Return is CHAR(13) + Line Feed is CHAR(10)

    well if i'm using space when is imported it would be using Space while i'm trying to used its original format..
    guess have to try those 'spesial character' instead..

    thanks

    1st NF - a table should not contain repeating groups.
    2nd NF - any fields that do not depend fully on the primary key should be moved to another table.
    3rd NF - there should be no dependency between non key fields in same table.
    - E. Petroutsos -


    eRiCk

    A collection of "Laku-abis" Ebook, Permanent Residence

    Access Reserved Words, a Classic Form Bug, Access Limitation, Know run Process and the Lock they hold in, Logging User Activity in MSSQL,
    Kill Database Processes

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width