To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=116536
------- Additional comments from [email protected] Sun Jan 23 22:38:46 +0000 2011 ------- Sorry, do not know what you mean by "table wizard created Table", thats not the issue in here, this is about fields, not tables, and besides that there are two different assistents, one for the build and one for the copyíng. isn't "wizard created" the words for build from the bottom? Even if it is the wrong idea by the user (which it is not, up to your roadmap) to make an existing field to a primary key-field, that should in no case result in dataloss. But the process is like that: if field-A should be a prim.key, the field-A-copy fails to be build, while the original field-A is already deleted. It looks as the concept is wrong. Martin --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
