RE: CPYTOIMPF and CSV Format

[rob@xxxxxxxxx]

Because no one has submitted a DCR?

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





Evan Harris <spanner@xxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/15/2003 02:20 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: CPYTOIMPF and CSV Format


Hi Jim

I have to agree with Ken here. Regardless of what might or might not be 
the 
database structure and the "correct" way of translating spaces or 
something 
else, by convention CSV files for as long as I can remember have removed 
trailing blanks between the commas.

Client Access downloads don't pad with blanks so why does the native 
utility ?

regards
Evan Harris

><snip>
>Your database isn't playing well with others, and you're blaming it on 
the
>system.
></snip>
>
>Actually.. It isn't even my database. It's 10.5gb of data within 15 files
>created by DDS on a legacy system. I don't know why the CPYTOIMPF 
wouldn't
>by default convert to variable length data since the rest of the world,
>others, seem to prefer such a format.
>
>Ken Slaugh (707) 795-1512 x118

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.