Issue 18610 - copy table auto pilot: usability issues when column type not matched automatically
Summary: copy table auto pilot: usability issues when column type not matched automati...
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC3
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Blocks: 20748
  Show dependency tree
Reported: 2003-08-25 08:36 UTC by Frank Schönheit
Modified: 2013-08-07 15:45 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2003-08-25 08:36:11 UTC
* start up the "copy table auto pilot" with the data described in issue 18609
* on the first page of the pilot, press "next"
* on the second page which allows selecting the fields to be copied, press the
button which copies *all* fields to the right
=> two error messages appear saying that no matching type could be found for
some columns

problem 1: Why one message for every column, instead of one message for *all*
problems which were encountered?
problem 2: There is no information whatsoever about the column types. Especially
the source type of the column would be very interesting to the user, as it
allows him/her to judge which target type would be best
problem 3: For the user, it's hard to understand what's going on. There is
simply a "no type could be found" statement. However, when the user travels to
the next page, there *is* a type chosen for the fields which caused the error.
Huh? No type could be chose, but we chose one, anyway?

I suggest an error message which
* lists all affected columns in one dialog
* presents the user with an information about the source type of the affected
* states something "please verify the choice made"
* contains an own help id (instead of the one of the generic SQL-error-dialog),
which allows more explicit help saying that for instance chosing the wrong type
could cause data loss while copying.
Comment 1 Frank Schönheit 2003-08-25 08:39:04 UTC
Comment 2 ocke.janssen 2003-09-15 13:24:54 UTC
Comment 3 marc.neumann 2003-09-29 11:19:37 UTC
"According to the roadmap
( this issue was retargeted to
OOo Later." 
Comment 4 hans_werner67 2004-02-02 12:17:31 UTC
change subcomponent to 'none'
Comment 5 Frank Schönheit 2005-04-13 09:31:45 UTC
blocking the meta issue