Paulo Vilela wrote:
I have opened this issue, but it was suggested that the discussion
should take place here...
I still think this change should be implemented . It is a question of
ease of use...
Paulo Vilela
-------------------
On OpenOffice.org Base we are allowed to import data from spreadsheets
or other
datas sources, but only in read only mode. This is possible using the
"connect"
option in the main OOo base menu. But many users want to be able to really
import the data and structure, and start using them on a read/write
mode,. This
is also possible, but only on a very non-intuitive way (copy date, nas
paste it
on the OOo menu). I has to struggle in order to understand how to do
it, and I
am an IT professional.
Suggestion: on the main OOo menu,there are already three options:
"create new",
"open existing" and "connect". There should be an "import" option as well,
enabling easy importing of data structures into OOo Base.
------- Additional comments from mechtilde Fri May 23 09:40:18 +0000
2008 -------
you can do ti via copying from one Base file to another.
You create one file connecting to e.g the *.csv. Then open another Base file
with the wanted DB backend. Then you can copy the data (the structure or the
whole table).
So I think this is a problem for [EMAIL PROTECTED] we should
continue
the dicussion there.
I agree, the copy/paste mechanism (even if done by drag-and-drop to a
new database) is not intuitive when industry terminology seems pretty
clear on this being an import. There also are (or were, the last I
checked) a number of things that work quite differently depending on the
source type; for instance, copied tables from Writer do not act the same
as copied ranges from Calc. (Quirky text padding coming in from a Writer
table is one of the oddities.) There should also be a warning at the
end of the table creation process if no primary key was specified
(HSQLdb treats any table without one as readonly).
To the need for Import, I'd add the need for Export; this inverse
operation seems to be available only by selecting Copy from the context
menu of a table or query (although clicking on the top left corner of a
displayed results set highlights all the data as selected, only the
first field of the first record is actually in the clipboard if you copy
from there). Then if you want an existing Writer table as the
destination, for example, you have to do a Paste Special outside the
table and select the RTF option, then use normal copy/paste operations
into the original table. At least this is what I've seen on WinXP with
OOo 2.3.1.
I went through a whole bunch of this kind of thing last year, but
between crunches on my end and new releases on the OOo end, I never
followed up with entering bugs/enhancements as I should have. At this
point, I probably should try out 3.0 with my scenarios and see what
happens. Maybe I can squeeze in the time somewhere -- or maybe enlist
somebody as a collaborator!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
