CSV Import Error

[Thelonius]

I'm using Sparx in-built CSV import facility v15.1. The documentation on CSV import / export is characteristically skimpy. The input is a properly formatted .csv file with heading names as per the spec. Using GUIDs to add tagged values.

Has anyone got any idea why this error message would be thrown? Are there any known limitations on input files that should be noted in the documentation but are not?



Thanks in advance.

[qwerty]

Google told me this:

The database file (mdb, Access 2000) was corrupted. I restore it from a back-up and now everything's fine.

Another one:

2
In my case, the data to be saved (string) was larger than the specified nvarchr(). Increasing the field size solved the problem

I would have guessed the latter...

q.

[Thelonius]

You were right, qwerty.

Using a needless but necessary process of tedious experimentation - I have confirmed there is an (undocumented) 255 character limit for text in any .csv import cell.

Anything longer than 255 characters:

   1. Causes the .csv import to fail
   2. Crashes Sparx EA.

Nice.

I would post a 'Change Request' to Sparx to please note this limitation into the documentation on the .csv import / export feature.

But past experience has shown this is like putting messages in bottles and throwing them off a long pier.

This condition should not have fallen through to cryptic system error level - the app should have caught it and posted an informative error message.

This especially should not have caused Sparx v15.1 to terminate.

But I digress. Problem solved. Thanks for playing.

[skiwi]

I think 255 is an EA limitation, its not in rfc4180 (ietf.org)

[qwerty]

It's probably a limitation of the underlying database column which is not properly caught by EA. In any case a crash is a bug to be fixed.

q.