Frank Schönheit - Sun Microsystems Germany wrote:
Hi Raw,
1. How to turn off the requirement of unique key or primary key, as
imposed in OO Base GUI, just before saving a newly designed table?
You cannot. For determining which row to update/insert in a table, OOo
needs to uniquely identify this row - this is what a primary key /
unique index is good for. You can still create tables without PK/UI, but
then you cannot update/add data.
Note that there are some backends which support data update even without
primary keys, for instance OOo's dBase implementation. This is because
those backends support another method of uniquely identifying a row
within a table, so-called bookmarks. However, if your backend doesn't
support this - and HSQLDB, OOo's default backend doesn't -, then you
need a PK.
2. Where to find out the documentation of design logic for this
additional restriction in OO Base GUI?
in the two paragraphs above :)
IIRC there's an FAQ entry explaining this, too.
3. How to find out the version of HQLDB engine embedded in an OO Base
installation?
The ugly way: Unzip your .odb file, and look into the
database/properties file. There's probably a runtime-way, too ...
Ciao
Frank
I think Base took a couple steps backward in the 2.0 release. I've been
going nuts trying to figure out how to update or add records and had no
idea that not having a primary key in my db was the problem. This thread
was my first clue, although the situation may have been documented
elsewhere, as indicated above. I sure couldn't find anything in the help
files to this effect.
Doesn't this make porting a Calc or Excel file to Base a lost cause,
except for viewing purposes? If you can't change the database how can
you add a primary key?
Some of us non-purists see nothing wrong with having duplicate records
in a flat-file database.
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
