Issue 18609 - table copy auto pilot: fields lost when no target type could be found
Summary: table copy auto pilot: fields lost when no target type could be found
Status: CLOSED FIXED
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: OOo 2.1
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords: regression
Depends on:
Blocks: 20748
  Show dependency tree
 
Reported: 2003-08-25 08:26 UTC by Frank Schönheit
Modified: 2007-09-20 09:06 UTC (History)
1 user (show)

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


Attachments

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:26:24 UTC
* create an ADO data source pointing to an MDB file of your choice
* have/create an arbitrary dBase data source
* create the table described in issue 18594
* open the data source browser, and drag'n'drop this table onto the "Tables"
container of the dBase data sorce
=> the "Copy Table" auto pilot pops up
* without changing anything, click "Create", to use the initial settings made by
the pilot
=> an error message pops up, saying something like "no corresponding type could
be found for table 'memo'"
* confirm this
=> the pilot jumps to the "Type formatting" page, where it suggests a new type
for the column
* press "Create", again
=> the table is created, but only with 3 fields instead of the original 8.

The problem is that when jumping to the "Type formatting" page, the pilot
"looses" all other fields after the one which caused the trouble. This can be
manually worked around by going back, adding all fields, and going forth, but
this isn't really obvious. There is no warning, indication, whatsoever, that the
pilot is currently *not* doing what the user wanted (namely: simply copy *all*
fields, including *all* data).
Comment 1 Frank Schönheit 2003-08-25 08:27:53 UTC
targeting
Comment 2 ocke.janssen 2003-09-15 13:26:07 UTC
.
Comment 3 marc.neumann 2003-09-29 11:19:05 UTC
"According to the OpenOffice.org roadmap
(http://tools.openoffice.org/releases) this issue was retargeted to
OOo Later." 
Comment 4 hans_werner67 2004-02-02 12:16:23 UTC
change subcomponent to 'none'
Comment 5 Frank Schönheit 2005-04-13 09:20:16 UTC
blocking the meta issue
Comment 6 ocke.janssen 2005-12-12 08:03:56 UTC
Fixed in cws dba30
Comment 7 Frank Schönheit 2006-05-11 14:27:11 UTC
fs-> msc: please verify in CWS dba30

re-open issue and reassign to msc
Comment 8 Frank Schönheit 2006-05-11 14:27:18 UTC
reassign to msc
Comment 9 Frank Schönheit 2006-05-11 14:27:22 UTC
reset resolution to FIXED
Comment 10 Frank Schönheit 2006-05-12 07:34:41 UTC
targeting to 2.0.4, as the fix is already available, and has meanwhile been
checked in in a 2.0.4-CWS
Comment 11 Frank Schönheit 2006-05-12 07:38:45 UTC
this used to work in some recent build -> keyword "regression"
Comment 12 Frank Schönheit 2006-05-12 07:41:13 UTC
targeting to 2.0.4, as the fix is already available, and has meanwhile been
checked in in a 2.0.4-CWS
Comment 13 marc.neumann 2006-05-18 07:56:21 UTC
verified in CWS dba30
find more information about this CWS, like when it is available in the master
builds, in EIS, the Environment Information System:
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fdba30
Comment 14 Frank Schönheit 2006-08-11 11:20:30 UTC
targeting to 2.1, since the fix is part of a CWS aiming for this release
Comment 15 marc.neumann 2007-09-20 09:06:36 UTC
Hi,

this is fixed in the current master. The current master is available at
http://download.openoffice.org/680/index.html

I close this issue now.

Bye Marc