Ocke Janssen wrote:
Moin Drew,
Drew Jensen wrote:
Will it be possible to generate Base files in OOo 3.0 that are
backwards compatible to OO.o versions < 2.4?
No. That isn't planed.
Thanks.
So I don't do again what I did with an image control question recently (
attempting to tell the person that wrote the code how their code works..
gees, the nerve of some people. ) let me ask another question.
Is this a technical concern then or a resources concern?
I can open a file created in 2.x under 3.0, update data and close the
file and it is still readable in 2.x. Change a query, tweak a form, or
add a report, save it and it is not. ( There is no warning that the file
format is about to be changed by the way, it just silently does it...an
RFE perahps? )
Open this ODF 1.2 formatted file in OO.o 2.4 and save it again, now it
is readable in 2.3.1 and below. ( again no warning that the file format
is being changed, would such a warning be relevant or even possible to
get into 2.4.1 given the date? )
Back in versions 2.3.1 and below it gets a little fuzzy as to what
happened to the file. If you try to open the file via File>Open the
select filter dialog opens, of course there is nothing there that will
help you. However if you do File>Database>Open then the base module just
quietly closes - no filter dialog box, no error box, it simply does
nothing. ( under XP anyway - haven't been able to test this on Linux yet )
This does not seem to fit with the precedence set by other modules -
Writer and Calc can each generate files of legacy formats. Indeed when
an .sdw file is opened in 3.0 and one selects File>Save a prompt (
assuming it is not explicitly turned off ) asks whether to covert the
file to ODF format or to keep the current format.
It was my understanding that one of the driving forces behind the
creation of the all-in-one file format was so that databases could be
more easily exchanged between different individuals. This then seems
like a problem as you can not expect that everyone is always running the
most current version of the application.
Even if a filter for the older file format is a problem then at least a
warning to the user that the file format is about to be changed seems
appropriate. Since there is going to be no way to address the lack of
information presented to the < 2.4 user if this file format change takes
place during an exchange of files then it becomes imperative, IMO, to
make it clear to the 3.x user.
Drew
--
OpenOffice.org User Community Forum: http://user.services.openoffice.org
United States PostgreSQL Association: http://www.postgresql.us/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
