2. ASPRunnerPro General questions
  3. [SOLVED]  Pipe Delimiter instead of Comma in CSV Files?
This topic is locked
[SOLVED]

 Pipe Delimiter instead of Comma in CSV Files?

 		7/23/2011 11:17:03 AM
ASPRunnerPro General questions
M
 mnegrete author

Is it possible to use a Pipe delimiter instead of a comma? Using the comma is problematic with fields that contain textual content using a comma.
Yes, you could put these fields in "quotes", but this is not an automated option from the system generating the CSV file and there are to many records to perform this manually. Creating an xls, unfortunately, is also not an option.
I'd welcome any suggestions or solutions anybody might have.
Thank you,

~Michael
Using ASPRunnerPro 6.2 (Build 5482)
Sergey Kornilov admin 7/24/2011

ASPRunnerPro automatically wraps fields with commas by double quotes. If this is not happening in your application post your application to Demo Account and open a ticket at http://support.xlinesoft.com sending your Demo Account URL. 'Demo Account' button can be found on the last screen in the program.
M
 		mnegrete author 7/28/2011



ASPRunnerPro automatically wraps fields with commas by double quotes. If this is not happening in your application post your application to Demo Account and open a ticket at http://support.xlinesoft.com sending your Demo Account URL. 'Demo Account' button can be found on the last screen in the program.


We are using ASPRunnerPro 6.2 (Build 5482), is this still applicable or only in version 6.3?
Sergey Kornilov admin 7/28/2011

It works this way since the beginning. If you do not wrap individual values any comma will break the whole CSV file.
M
 		mnegrete author 7/29/2011



It works this way since the beginning. If you do not wrap individual values any comma will break the whole CSV file.


I think I may not have explained myself clearly. The issue is when importing a CSV file into an ASPrunner Pro application. We've written an application that requires the data to be imported via a CSV file of which v6.2 only allows a comma delimiter. This is where the problem occurs, because when a field has textual content that includes a comma, it sees it as a break for a new field, thereby causing the import to fail. I understand ASPRunner Pro v6.3 has an "import_functions.asp" file where the delimiter can be edited, but moving our application to v6.3 is not an option at this point.
Any suggestions would be greatly appreciated.
Thank you,

~Michael
Sergey Kornilov admin 7/29/2011

Michael,
thank you, I see what you mean.
As far as I can see you have opened a ticket already. Jane will follow-up with you.