On 9/19/06, Dan Lewis <[EMAIL PROTECTED]> wrote:
What you are describing is not a simple project. What type of
Fields would require all of these relationships?
Well... I've worked mainly with PostgreSQL, MySQL and SQLite
databases, and in this contexts these complicated webs are fair common
:)
(Ok, it can be a sign that I'm not thinking by the "OOo Base" way at all :p)
There is probably a
way to do this, but without more specific information as to the
purpose for this database, it would be very hard to answer your
question.
Ok, I explain!
I must have a table for representing an employee on an company. In
this table, each employee must have an superior employee, his/her
boss. So, I'm trying to create an "superior" at "Employee" table for
referencing an element of "Employee" table itself: the boss of the
current employee. It's the case of recursive relationship.
Another problem: I have a table of states (subregions of a country,
provinces) called "State" on my project. Each employee lives on a
state, of course, but each employee has a identifier document called
"RG" which has tree fields: an emitent, a number and the state of the
emitent. So, for each employee, I must have the two first fields and
another foreign key to the "State" table - and I can't create the
relationship between the RG state field and the state primary key,
once that I've created a relationship betwee employees and states
before.
Have I been more informative now? :)
Dan
Again, I'm sorry for my simplistic questions, but I'm really thankful anyway :)
--
Adam Victor Nazareth Brandizzi
http://brandizzi.googlepages.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
