Hello,

Ferry Toth schrieb:
I agree!

Note that the table wizard generates exactly these tables. The Wiki shows how to connect the relationships http://wiki.services.openoffice.org/wiki/Standard_Distributed_Schema.

That would lead to a database example like "Northwind" from MS Access. But such a database doesn't fill my purpose. I want a very small database, which is suitable for pupils. A database
(1) they can generate and fill themselves.
(2) which I can use to explain fundamentals of database design.
(3) by which they can learn all parts of the module, without being irritated with nearly hundred fields in the database
(4) for which I can define small tasks and the pupils can try out things.


So what we need next is forms and reports and possibly clever Calc sheets that show how to retrieve and analyze data.

That is not the real problem, but filling the database with data. Do you really think, that OOo community will translate the data, when it has the size of a "Northwind"-database? And it needs a significant number of records to give reasonable results, therefore the number of tables and fields must be small.


Problem: If we try to develop such a database together we need a version control system. When it's done it needs to be translated to every language OO supports.

My idea: we need to develop a Basic script that generates the whole database with everything in it. The Basic code is text and can be maintained as all other code. The localization text should be separated for easy translation.

Such things will be the second step. First step is an agreement on the kind of database. But probably the different requirements cannot be met with one single database.

kind regards
Regina


Ferry

Tim wrote:
In my opinion, it would be better to have a business database with customers, vendors, products, services, invoicing(reports), sales reports, sales forms, etc. This would cover most cases that users would be creating and would be a better platform to be an example.

Tim

Uwe Fischer wrote:
Hi,

for the Base application help it would be very helpful to have a sample database with some sample records. Help steps can then refer to those tables. Currently, every Base help text needs to start with something like "imagine you have a database with the following structure... and there are fields with the following names ... and you have defined a query like this ...". This makes writing short how-to-do steps really annoying (and may be the main reason why there aren't any such short and quick guides)

Uwe

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to