Confused

[LiveOak]

And what exactly is a record in the New Position db? (and how is this different from an "Old Position" or when is a "new" position no longer new?)

-bd

[nati]

Hi Chuck,

Let's say we have a new position opening up and also someone is retiring so we have two "new" positions to fill. The board writes up a description for the jobs; pay scale, requirements, etc. These are put into the New Position db and are kept there until they are filled or removed or updated. When they are filled then the new hire receives the information from the database in his/her request (it could be request for hire as first line item, reviewed as second, hired as third).

This differs from other requests. Say we have a staff who is up for a pay raise. In request db first action line item is submit pay increase then review then accept or deny. These are created in the request db by entering the info in the action db portal (allow creation of related records). However the new is pulling information from the New db. We could have a dozen or more New items waiting and we want to track them; update, etc. In the other requests there is not information stored, it's just entered as we go by allowing created related records.

I thought that the Request to New was a many to many but in fact I believe it's a one to one. Does that make sense?

Thanks,

nati

[ June 22, 2001: Message edited by: nati ]

[ June 22, 2001: Message edited by: nati ]

[nati]

Hi,

I'm designing a staff action db for our grade school.

Have db's personnel, request and action. Requests are for pay adjustments, promotion requests, leave, etc.

Design is one personnel to many requests to many actions (request received, emailed to appropriate party, etc). Actions are created from Request db. All but one action is a drop down of different types (request received, emailed to....etc).

The one that is different is New Position. Here we have a db and create a new entry for a new position and it has many things associated with it (committee to approve, review process, etc). When someone is selected we then create a new request for this new position, either creating a new person if they are coming from outside, or new request for existing person, with their new position being filled in from the New Position db.

We do this manually righ now but was wondering how to incorporate the New Position db in there.

Any help appreciated.

Nati

[ June 22, 2001: Message edited by: nati ]

[LiveOak]

Actually this is Brent,

I sounds like you have a one-to-one relationship from New Position to Requests or a one-to-many from New Position to Actions. At the expense of more fields per record, you could make each New Position entry just a special type of Request record. New Positions could be found under script control and displayed on a special layout to make it appear as if they are stored in a separate file, not mixed in with other requests. Anytime you have a one-to-one relationship, you have to ask yourself if the data should be combined in the same file.

-bd

[nati]

thanks... Brent!

I'll give it some thought... appreciate the new way to look at it.

nati