Export to csv having issue with import to SQL(Remedy)

[N. Graves]

Thanks for taking the time to read this note.

I have a Access inventory collection tool that I have automated to
build and Export to a CSV file. In the database I have several fields
that are large text fields for comments. When I'm collecting data I
have set the <Enter> button to move to next line instead of the
default.

We are trying to import this CSV data file in to a Remedy SQL server
using the Remedy Import tool. This import fails if the user in the
Collection tool uses the <enter> button to format the data. It looks
like it is adding a <cr><lf> to the row of data and then moves to the
next line of information.

Is there an easy solution to the issue? .. other than not letting the
user format the data?

N. Graves

[Larry Linson]

If your Remedy Import chokes up on Cr-Lf, then you will need to prevent it
being there or remove the ones that are there. Because, if you configure for
Enter to go to the next line within the Text Box, you will be entering the
"NewLine" which is a combination of "Carriage Return" and "Line Feed".

The Replace function may be a handy one for this circumstance; if you are
using an earlier version of Access than 2000, you can likely find a
user-coded Replace function with a search of the archives at
http://groups.google.com.

Larry Linson
Microsoft Access MVP
"N. Graves" <ng*****@REMOVEyahoo.com> wrote in message
news:3l********************************@4ax.com...

Thanks for taking the time to read this note.

I have a Access inventory collection tool that I have automated to
build and Export to a CSV file. In the database I have several fields
that are large text fields for comments. When I'm collecting data I
have set the <Enter> button to move to next line instead of the
default.

We are trying to import this CSV data file in to a Remedy SQL server
using the Remedy Import tool. This import fails if the user in the
Collection tool uses the <enter> button to format the data. It looks
like it is adding a <cr><lf> to the row of data and then moves to the
next line of information.

Is there an easy solution to the issue? .. other than not letting the
user format the data?

N. Graves

[Dimitri Furman]

On Aug 04 2004, 07:58 pm, N. Graves <ng*****@REMOVEyahoo.com> wrote in
news:3l********************************@4ax.com:

I have a Access inventory collection tool that I have automated to
build and Export to a CSV file. In the database I have several fields
that are large text fields for comments. When I'm collecting data I
have set the <Enter> button to move to next line instead of the
default.

We are trying to import this CSV data file in to a Remedy SQL server
using the Remedy Import tool. This import fails if the user in the
Collection tool uses the <enter> button to format the data. It looks
like it is adding a <cr><lf> to the row of data and then moves to the
next line of information.

Is there an easy solution to the issue? .. other than not letting the
user format the data?

TextExport class from http://www.users.cloud9.net/~dfurman/code.htm will
export your text to a delimited file, optionally replacing CRLFs with some
other string (let's say a space, or possibly standalone LF or CR). This
will avoid the import problems, but of course may reformat the text in an
undesired way.

You may replace CRLFs with some token string during export, then once the
data is imported, replace the token string with CRLFs.

--
remove a 9 to reply by email

[N. Graves]

In my situation this may be overkill... but thank you very much for
your input and I will keep this note for future reference!!!

Thanks

N. Graves

On Thu, 05 Aug 2004 11:48:46 -0000, Dimitri Furman
<df*****@cloud99.net> wrote:

On Aug 04 2004, 07:58 pm, N. Graves <ng*****@REMOVEyahoo.com> wrote in
news:3l********************************@4ax.com :

I have a Access inventory collection tool that I have automated to
build and Export to a CSV file. In the database I have several fields
that are large text fields for comments. When I'm collecting data I
have set the <Enter> button to move to next line instead of the
default.

We are trying to import this CSV data file in to a Remedy SQL server
using the Remedy Import tool. This import fails if the user in the
Collection tool uses the <enter> button to format the data. It looks
like it is adding a <cr><lf> to the row of data and then moves to the
next line of information.

Is there an easy solution to the issue? .. other than not letting the
user format the data?

TextExport class from http://www.users.cloud9.net/~dfurman/code.htm will
export your text to a delimited file, optionally replacing CRLFs with some
other string (let's say a space, or possibly standalone LF or CR). This
will avoid the import problems, but of course may reformat the text in an
undesired way.

You may replace CRLFs with some token string during export, then once the
data is imported, replace the token string with CRLFs.

[N. Graves]

With the help of the iif Perfect was reached... thanks for your input.

N. Graves
On Thu, 05 Aug 2004 02:32:33 GMT, "Larry Linson"
<bo*****@localhost.not> wrote:

If your Remedy Import chokes up on Cr-Lf, then you will need to prevent it
being there or remove the ones that are there. Because, if you configure for
Enter to go to the next line within the Text Box, you will be entering the
"NewLine" which is a combination of "Carriage Return" and "Line Feed".

The Replace function may be a handy one for this circumstance; if you are
using an earlier version of Access than 2000, you can likely find a
user-coded Replace function with a search of the archives at
http://groups.google.com.

Larry Linson
Microsoft Access MVP
"N. Graves" <ng*****@REMOVEyahoo.com> wrote in message
news:3l********************************@4ax.com.. .

Thanks for taking the time to read this note.

I have a Access inventory collection tool that I have automated to
build and Export to a CSV file. In the database I have several fields
that are large text fields for comments. When I'm collecting data I
have set the <Enter> button to move to next line instead of the
default.

We are trying to import this CSV data file in to a Remedy SQL server
using the Remedy Import tool. This import fails if the user in the
Collection tool uses the <enter> button to format the data. It looks
like it is adding a <cr><lf> to the row of data and then moves to the
next line of information.

Is there an easy solution to the issue? .. other than not letting the
user format the data?

N. Graves