Can't Upload Data from CSV File Because Table has a 200 Row Limit

1. 64

   eugbugposted 7 years ago

   My CSV data has 100 true rows, but cells have CR LF pairs creating two lines per cell, so I'm assuming this is what's causing it to exceed the 200 row limit

   replyreport
2. 64

   eugbugposted 7 years ago

   I think what's happening is that the CR LFs are screwing up the CSV output, so it's a problem with my file.
   Any Excel experts have any ideas on how to avoid this problem?

   replyreport
   1. 78

      Natalie Frankposted 7 years agoin reply to this

      As long as we are talking about the cvs file anyone know how to save it and keep the top row with the column titles?  This row went about halfway down the table then froze in place there.

      replyreport
3. 64

   eugbugposted 7 years ago

   Commas are the delimiters, but I'm guessing on import, a CR or LF or both are interpreted as the end of a row of cells. Encountering these in cells, forces the import to put everything in a single column.

   replyreport
4. 64

   eugbugposted 7 years ago

   Is there any way I can have two lines in a cell (without forcing a word wrap?).

   replyreport
   1. 66

      lobobrandonposted 7 years agoin reply to this

      A word wrap is when the text moves onto the next line when it's too big to fit on the previous line. Do you mean you want to merge two cells of text say:
      Cell A:
      Hello
      
      Ceall B:
      Hola
      
      New Cell:
      Hello
      Hola
      
      OR
      
      New Cell:
      Hello Hola

      replyreport
      1. 64

         eugbugposted 7 years agoin reply to this

         I'm making a table with dimensions. Each cell contains an inches value in decimal plus the equivalent fraction value to the nearest 1/16".
         I can do it in Excel and format the cell in a formula, including an LF in the middle and it works fine (CR doesn't seem to be required), but when I export to a CSV file and import into a HubPages table, the LFs in cells are being interpreted as end of rows.
         This is the formula - I'm concatenating everything together.
         
         =TEXT(A3/SIN(180/$B$2*(PI()/180)),"##.00") & CHAR(10) & "(" & TEXT(MROUND(A3/SIN(180/$B$2*PI()/180),1/16), "# ?/??") & ")"
         
         This is what it looks like in Excel
         
         
         I think I'll just add a space instead of a new line, but the latter looked better.

         replyreport
5. 64

   eugbugposted 7 years ago

   A forced word wrap to generate a CR LF would be an option, but it's a messy way of doing it.

   replyreport
6. 64

   eugbugposted 7 years ago

   With the number of rows reduced to 179 and 7 columns, there still seems to be a problem importing. Everything gets put into 1 column.

   replyreport
7. 64

   eugbugposted 7 years ago

   I used an online CSV viewer and it worked fine, so it seems there's a bug in the CSV import code on HubPages.

   replyreport
8. 64

   eugbugposted 7 years ago

   As an aside, Wordpad adds a CR when it encounters an LF when viewing a file and there's no option to turn this off. Use a proper hex editor if you need to view the character codes in files.

   replyreport
9. 0

   Beth Eaglescliffeposted 7 years ago

   A possible work-around the problem: Instead of inserting a table, you could do a screenshot (or 2 or 3 screenshots so that the figures are readable in the hub) and then use photo modules.

   replyreport
   1. 64

      eugbugposted 7 years agoin reply to this

      That's what I ended up doing Beth until the bug is fixed. A screen copy saved as a JPG is fine, but I discovered some online converters which will generate a JPG from an Excel file that has lots of rows and runs off screen.

      replyreport
10. 66

    lobobrandonposted 7 years ago

    Hmm that's weird. Did you try out just one online CSV viewer? Maybe that one is special and not the norm?
    
    Also, a table is definitely better than a picture for many reasons.

    replyreport
    1. 64

       eugbugposted 7 years agoin reply to this

       No I just tried one. It gives the option of using LF or CRLF for detecting end of row. So  I tried to confuse it by adding back in an LF in one cell and it worked fine. So presumably it could tell the difference between an LF and a CRLF at the end of the line. Then I tried to confuse it further by setting LF for end of row detection so that it would think LF in a cell was the end of a row but that still worked. So I guess it had kept a record of the number of columns from previous rows and realised that the LF in a cell wasn't really a row terminator.

       replyreport
       1. 66

          lobobrandonposted 7 years agoin reply to this

          Makes sense.

          replyreport