More robust importing from imperfect spreadsheets

SOFA Statistics version 0.9.23 makes importing data from spreadsheets (and csv) much more robust. In particular, it copes better with inconsistent data types in a single field and give the user a choice as to which to use:

Choosing data type

Choosing data type

The latest version also has a much more reliable method of identifying and extracting date data from ods (OpenOffice Calc, Gnumeric, Google Docs spreadsheets).

Other changes include:

  • If no change to table design when clicking Update, get a message that there was no change instead of no response.
  • When opening data tables, the read only checkbox is ticked or unticked according to whether showing the demonstration table or not when in the default sofa database.
  • Now handles PostgreSQL databases with different schemas.
  • When run in console, SOFA produces much more useful input on progress during initial stages and on any error encountered.
  • Height setting algorithm for data editing/display grid now copes with taller e.g. double height, taskbars in Windows.
  • More reliable method used for identifying the folder location of SOFA.

There are also numerous bug fixes:

  • All lines in multi-line text cells are now imported from ods spreasdsheets correctly.
  • Errors when getting project settings file at start return useful message and don’t fail because tried to use msgbox before the GUI application is running.
  • Better handling of errors when identifying date format. Falls back to a reasonable default.
  • Fixed error preventing message being shown when unable to change database details e.g. selecting a different db in the drop-down.
  • Fixed bug in legend of auxiliary clustered bar charts when long value labels. Now has automatic line splitting.
  • Correct initial display of csv data when importing if missing cells in some rows.
  • Majorly reduced impact of bug when creating report tables using numbers with more decimal points than python displays when converting to text e.g. into an SQL statement ready for execution.
  • CSV importing now provides useful error messages if actually an Excel spreadsheet saved as a csv with Excel features preserved (i.e. a faulty csv file). Also copes better with faulty delimiters being manually supplied.

Comments are closed.