Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook
Devcon 2020 Goes Virtual! LEARN MORE >

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Maintaining Carriage Returns after export to CSV

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #1

    Maintaining Carriage Returns after export to CSV

    Hi,

    I have just taken an indepth look that the forum, but i cannot see any answers to this. Perhaps there isn't one, but i will ask anyway.

    Is it possible to export a table to CSV and maintain the carriage returns within a memo field?

    Thanks,

    Denis
    Tags: None
    #2
    Re: Maintaining Carriage Returns after export to CSV

    Anyone?

    Comment

      #3
      Re: Maintaining Carriage Returns after export to CSV

      Yes this is doable. You will most likely need to write your own export routine to handle it.

      Code:
      Table Structure
Field1,c,10
Field2,c,10
Field3,m

      Record1
      Code:
      "Fld1_data","Fld2_data","Fld3_Memo_data"
      Lets assumes that Fld3_Memo_data is 3 lines, so it contains 2 crlf()'s.

      Your export file could take the format of...
      Code:
      Fld1_Data,Fld2_data,Fld3_memo_data_line1
Fld1_data,Fld2_data,Fld3_memo_data_line2
Fld1_data,Fld2_data,Fld3_memo_data_line3
      Andrew

      Comment

        #4
        Re: Maintaining Carriage Returns after export to CSV

        Originally posted by den1s View Post
        Hi,

        I have just taken an indepth look that the forum, but i cannot see any answers to this. Perhaps there isn't one, but i will ask anyway.

        Is it possible to export a table to CSV and maintain the carriage returns within a memo field?

        Thanks,

        Denis
        Do any of these options give you choices that help??
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein

        http://www.iadn.com/images/media/iadn_member.png

        Comment

          #5
          Re: Maintaining Carriage Returns after export to CSV

          I'm skeptical this can be done without much more work. In the typical CSV formatted file the crlf pair delimits the record. One record per line, in other words. You're wanting a variable number of lines per record. Most would not call that a CSV formatted file.

          The key questions are (a) if the data is being moved to CSV so that it can be imported by a different application, will that application be able to import multi-line records; and (b) if so, are you willing to write the code necessary to "delimit" your records differently?

          Comment

            #6
            Re: Maintaining Carriage Returns after export to CSV

            Denis,

            Why?
            Steve Wood
            See my profile on IADN

            Comment

              #7
              Re: Maintaining Carriage Returns after export to CSV

              What is the source data? If it is Excel and being created by converting it to a csv file for import then this makes things unnecessarily difficult.
              It is much easier to import "memos" direct from Excel. If the source can export to Excel, then I recommend you try this first.
              Garry

              Comment

                #8
                Re: Maintaining Carriage Returns after export to CSV

                All,

                The reason i am trying to achieve this is because my customer wants to export data to PDF (easy) and Excel (Hmmm).

                Unfortunately, Excel has a 255 character limitation, so i cannot use xls files. When i use CSV there appears to be no character limitation. Perfect!. The only snag is that within a memo field with lots of text that has Carriage Returns, end up being one continuas line of text. Messy.

                The data will be viewed using excel 2003.

                I hope this helps.

                Denis

                Comment

                  #9
                  Re: Maintaining Carriage Returns after export to CSV

                  How often do you need to do this import?
                  If it is only once or rarely, import Excel data into Access, then import from Access to Alpha with AlphaDAO.
                  Garry

                  Comment

                    #10
                    Re: Maintaining Carriage Returns after export to CSV

                    Garry,

                    Its a regular export.

                    Denis

                    Comment

                      #11
                      Re: Maintaining Carriage Returns after export to CSV

                      Denis,

                      You want to do the opposite, you need to replace carriage-returns with soft-returns. You can probably do this with an export operation, but like to spell them out. Here is an example. The important part is the line with stritran(). It puts quotes around the memo field text and replaces any crlf with chr(10).

                      a_tbl = table.open("[PathAlias.ADB_Path]\test")
                      query.order = ""
                      query.filter = ".T."
                      query.options = "I"
                      a_tbl.query_create()
                      a_tbl.fetch_first()
                      lst = ""
                      while .not. a_tbl.fetch_eof()
                      lst = lst + alltrim(a_tbl.somefield)
                      lst = lst + ","
                      lst = lst + "\"" + stritran(a_tbl.mymemofield,crlf(),chr(10)) + "\""
                      lst = lst + crlf()
                      a_tbl.fetch_next()
                      end while
                      save_to_file(lst,"c:\test.csv")
                      Steve Wood
                      See my profile on IADN

                      Comment

                        #12
                        Re: Maintaining Carriage Returns after export to CSV

                        Steve,

                        Thank you. That worked, however, im not sure how i can incorporate this code into my existing export script. Can you show me where i should put this please. Also what should go into a_tbl_somefield?

                        Code:
                        dim exportfile as c
dim filename   as c
exportfile = "InterfaceReport.csv"
filename = session.session_folder + exportfile
dim a_tbl as p

a_tbl = table.open("[PathAlias.ADB_Path]\tbl_obj_int_link.dbf")
query.order = session.sortby
query.filter = filter
query.options = "I"
a_tbl.query_create()

[B]'Maintain carriage returns[/B]
a_tbl.fetch_first()
lst = ""
while .not. a_tbl.fetch_eof()
lst = lst + alltrim(a_tbl.somefield)
lst = lst + ","
lst = lst + "\"" + stritran(a_tbl.Int_Desc,crlf(),chr(10)) + "\""
lst = lst + crlf()
a_tbl.fetch_next()
end while
save_to_file(lst,"c:\test.csv")
[B]'End of code[/B]

export.type = 0 
export.names = .T.
export.file = filename
export.options = ""
export.field_sep = ","
export.record_sep = "<CR><LF>"
export.fields = 7
export.field1 = "Link_ID"
export.field2 = "Int_Name"
export.field3 = "FrObject"
export.field4 = "ToObject"
export.field5 = "Flowtype_ID"
export.field6 = "Int_Med_ID"
export.field7 = "Int_Desc"

a_tbl.export()
if file.exists(filename)
	response.redirect(session.session_url + exportfile )
end if
                        Thanks,

                        Denis

                        Comment

                          #13
                          Re: Maintaining Carriage Returns after export to CSV

                          By somefield I just meant whatever fields you wanted to export. You are combining methods, using both in the same script. If you make it work it would run in any dialog or a5w page.
                          Steve Wood
                          See my profile on IADN

                          Comment

                            #14
                            Re: Maintaining Carriage Returns after export to CSV

                            Steve,

                            Using my modified script (above) two files are being created, "InterfaceReport.csv" and "c:\test.csv".

                            How can i incorporate your code so that the data and all seven fields are self contained within exportfile = "InterfaceReport.csv"?

                            YOUR CODE
                            Code:
                            'Maintain carriage returns
a_tbl.fetch_first()
lst = ""
while .not. a_tbl.fetch_eof()
lst = lst + alltrim(a_tbl.somefield)
lst = lst + ","
lst = lst + "\"" + stritran(a_tbl.Int_Desc,crlf(),chr(10)) + "\""
lst = lst + crlf()
a_tbl.fetch_next()
end while
save_to_file(lst,"c:\test.csv")
'End of code
                            Thanks,

                            Denis
                            Last edited by den1s; 05-27-2009, 05:44 AM.

                            Comment

                              #15
                              Re: Maintaining Carriage Returns after export to CSV

                              I have been trying to get merge the two pieces of code together for most of the day. I have hit a major brick wall and now need to seek some expert advise.

                              Will the two pieces of code (above) work together to create a single CSV file. If not, how can i add more fields to Steve's code?

                              Any help on this will really be appreciated.

                              Thanks.

                              Denis

                              Comment

                              Previous 1 2 template Next
                              Working...
                              X