• Client crashes while importing data from Excel

    By Rudolf Haller 2 decades ago

    This occurs when running under Client Version 7.0.3:

    When importing an Excel-spreadsheet which contains all about 3.500 rows of data, the DMA crashes after processing about 35% of the data rows.



    This occurs when running under Client Version 8.5:

    A message box appears with Type mismatch. The client doesn't crash.



    It would be gread to have a record counter to locate the record which probably has wrong or invalid data contents. Thanks!

    • Please email me the spreadsheet

      By David Jeyachandran 2 decades ago

      Thanks Rudolf,



      I can look at the error reporting and see if it can flag the row that it fails. If the spreadsheet is not confidential, could you please email this to me. You can email me by using "Email Chef" button. This would be helpful in identifying the cause and preventing future crashes.



      You may want to check if there are any cells with an Excel errors eg. #Error



      Regards

      David

      • By Rudolf Haller 2 decades ago

        Hi David,



        unfortunately, the data in the spreadsheet are confidential. I checked it for cell errors, but there were no matches found. Everything in the table seems to be okay. I tried with an other data pump nsf and with it the import works. I think, it would be great if you could "install" an error handler which checks the condition of the data which the current cell contains.



        It think, this is the reason the crash causes.



        BTW: I hope, you will give the DMA a robust data-reading engine for excel, because your tool is great!



        Regards

        Rudi

    • Could be #NA value

      By Puhn Dunners 2 decades ago

      When I did the tests with Excel to Notes, LN crashed on a line with a #NA value.



      Hope this helps.

      • Fixed in the soon to be release version

        By David Jeyachandran 2 decades ago

        Hi Puhn,



        You are right. I have found a way to eliminate this bug. This will be released after I do some testing this weekend.



        The fix involves checking excelcell.text before getting excelcell.value. If excelcell.text contains a "#" I flag an error without getting the excelcell.value.



        Kind Regards

        David