Solution for excel import problems in Path 4.2 – "combined values…must be unique"

Deliver geospatial models direct to decision makers with SyncroSim Forums ST-Sim & State-and-Transition Simulation Models Solution for excel import problems in Path 4.2 – "combined values…must be unique"

  • This topic is empty.
Viewing 1 post (of 1 total)
  • Author
    Posts
  • #1666
    leonardo-fridleonardo-frid
    Keymaster

    Some Path users have reported a problem importing files from excel where they receive an error that "The combined values for the folowing columns must be unique: …" Yet the values in their excel file they are importing truly are unique.

     

    This is caused by a problem with the Microsoft ACE OLEDB provider that we use in Path.

     

    Workaround: If you have "mixed" values in a worksheet column (for example "Stratum") and some of them are NULL, put the records with non-NULL values at the top of the worksheet.  This will cause the driver to import all values correctly.

     

    Note:  Upgrading from Path to ST-Sim, our latest version of software for developing state-and-transition simulation models, will solve this problem as ST-Sim does not use the ACE driver.

     

    Detailed Explanation: If the first 8 rows in a column of an Excel WorkSheet are NULL – and the remaining rows include non-NULL values – the import may not work correctly.  The reason for this is that the ACE OLEDB provider that we use to get the worksheet data from Excel uses the first 8 values for a particular column to guess the data type for the entire column.  If the data type is guessed to be NULL, then subsequent non-NULL values are imported as NULL.  The reverse is not true:  if the first 8 values are non-NULL, then subsequent NULL values are imported correctly.  

     

     

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.