Hi Regina, > I had a look at it. The new UI seems to focus on using existing > csv-files and it looks good for those cases. But why restrict it to only > existing csv-files?
Finally, it would need a full-blown column editor in the dialog (including addition, removal, and ordering of columns). This would make the UI more complex, thus, the iTeam's decision on this was to not have it. I take your argueing as a vote *pro* this feature then :). > I had transformed the biblio table in such a linked table and it was > very troublesome to do all the work with direct SQL. I would like to see > this additions: > In step "table" (1.3.1) allow to enter the name of a not existing > csv-file. OOo will generate that file then. > In step "table" (1.3.3) give the possibility to copy the column > definitions of an existing table out of the same database-document. Version 0.3 of the spec (not yet published) contains a "Future Task" which suggests some "Paste Special" functionality, where an arbitrary table from the clipboard could be pasted as linked table. The column information would be pre-filled, and the user would choose a new file (and do the file/format-related settings only). This would then of course also work with queries, as suggested by Andrew (though it would not be as obvious as a context menu entry, admittedly). This would also address the scenario you described, wouldn't it? Thanks & Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Database http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
