* extract the attachement into an empty folder
* create a new dBase data source, pointing to this folder
* open the data source browser, therein display the bugdoc table
  The table contains a column "text_id", and a unique index for this table
* select one of the two records of this table, drag and drop them into empty
space of the table view
=> this starts copying the records
=> 3 error messages:
   - Duplicate value found in column 'text_id'
   - Function sequence error
   - An error occured. Do you want to continue copying?

(The bug is independent on the concrete database type, I could also reproduce it
with a MySQL database.)

This definately are too much error messages :). I think we have several problems
here, with different severity:
- When copying one record fails, we should only show _one_ message for this: The
  "Function sequence error" message is not only senseless (because it doesn't
  tell the user anything), but it also indicates that the copy process continues
  to do something, though it already failed
- We should not ask the user if s/he wants to continue copying if we are already
  dealing with the last record.

Of course it would be really really cool if the copy process would
* detect that
  - the source and the destination table are the same
  - the table contains a unique index or a primary key
* properly recognize that this means that copying will _definately_ fail, and
  offer the user a set of choices how to handle this, up to allowing the user
  to explicitly specify new values for the key columns for every record to
  be copied. But this probably is a topic for a separate issue :)