Hello Regina,
try this: build a query on wathever table, with as many fields as you
like. You'll see that each field of your query will be updatable. But if
you create a many-to-one relationship between that table and a second
one, your query will automatically turn into a read-only one. This is,
from my point of you, a very hard limit.
There is an issue (#53377) on this trouble, opened since Aug 16 2005.
You can find also an example, inside it.
About your further remarks, I'm sure that relationships between queries
or between queries and table would give us much more flexibility, in any
project, without unespected troubles. I worked this way for years, with
Access, and I was always happy. No problems, at all.
Thanks for your reply and best regards,
Franco
Regina Henschel ha scritto:
Hello Franco,
Franco Fornari schrieb:
Hello Frank,
this is my first message to this group, even if my subscription goes
back to the past year.
I am an old MS-Access user and programmer for my own pourposes, and I
am currently evaluating to migrate to Base.
I'd like to know your opinion (and of those members interested to
this matter) on some functionalities that are still very limited in
Base.
I'm referring, mainly, to the following:
1. queries built on more than one table are totally not editabile;
What do you mean with "not editabile"?
I'm annoyed, that OOo chances my INNER JOIN to a WHERE clause.
2. any relationships between queries or queries and tables are not
allowed
Why should it be allowed? Isn't a FOREIGNKEY a CONSTRAINT on a _table_?
3. queries built on others queries or queries and tables are not
allowed;
If you want that, you can generate a view from your query.
3. in case of external databases, such as datasheets, the resulting
tables in Base are read-only,
For csv-tables you can use a texttable.
but the worst thing is that the user
cannot create any relationship between that tables and consequently
any queries with more than one table.
I'm pretty confident that these limitations can (and will) be solved,
sooner or later (some issues were opened, too, since the past year),
but what sounds strange to me is the silence of the members of this
community. It seems that this matter were as marginal, or had a very
low priority inside the whole project.
I think that it is not a problem of priority. But the whole time, work
on Base is going on, is very short compared with the other modules.
And of cause you should not compare it with Access where lots of
people had paid for it for more than ten years.
I have always thought that this kind of functionalities make the
difference between relational databases and flat ones. Am I wrong?
No, I think too, that relationships are important. But I do not
expect, that they are possible on Calc-tables. There is so easy import
and export to Calc, that you can use a real database instead of
Calc-tables.
Once, many years ago, I somewhere read that the most of users
actually use Access as a flat database and not as a relational one.
Perhaps this is still true, also for Base?
I don't know, but it is likely the same as for Writer, which is used
as a typewriter.
kind regards
Regina
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.4.4/319 - Release Date: 19/04/06
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
