Calculated field in Forms

Hello-
I would like to see how I can add a calcualted field to my forms that would
show me when an employee is eligible for benefits. I have employee who
qualify in 30 days, others are 90 days.

Your help is appreciated!
Thank you,

On Wed, 14 Apr 2010 15:27:02 -0700, dar wrote:

Hello-
I would like to see how I can add a calcualted field to my forms that would
show me when an employee is eligible for benefits. I have employee who
qualify in 30 days, others are 90 days.

Your help is appreciated!
Thank you,

30 days from.... what? Hiredate? How can you determine (from data in the
table) whether it should be 30 or 90 days? What do you want to see on the
form: a date, the word ELIGIBLE in a textbox, both, something else?

Remember - we know nothing about either your business or your database except
what you tell us.

--

John W. Vinson [MVP]

Yes, managers are 30 days from hire date, clerks are 90 days from hire date.

"John W. Vinson" wrote:

On Wed, 14 Apr 2010 15:27:02 -0700, dar wrote:

Hello-
I would like to see how I can add a calcualted field to my forms that would
show me when an employee is eligible for benefits. I have employee who
qualify in 30 days, others are 90 days.

Your help is appreciated!
Thank you,

30 days from.... what? Hiredate? How can you determine (from data in the
table) whether it should be 30 or 90 days? What do you want to see on the
form: a date, the word ELIGIBLE in a textbox, both, something else?

Remember - we know nothing about either your business or your database except
what you tell us.

--

John W. Vinson [MVP]
.

On Fri, 16 Apr 2010 09:32:01 -0700, dar wrote:

Yes, managers are 30 days from hire date, clerks are 90 days from hire date.


That's a business rule.

It's not a database rule.

I can see how you would enforce that in your office, but since you have chosen
not to post any information about your tables, I cannot tell how you would
enforce it in a database.

I'd love to be able to help, but I can't unless you tell me what's in your
database!
--

John W. Vinson [MVP]

Sorry about that I am new to this forum.

Tabel: Employee

My fields a
LName
FName
Hire Date

I would like to set the rule based off of the Hire date.

"John W. Vinson" wrote:

On Fri, 16 Apr 2010 09:32:01 -0700, dar wrote:

Yes, managers are 30 days from hire date, clerks are 90 days from hire date.


That's a business rule.

It's not a database rule.

I can see how you would enforce that in your office, but since you have chosen
not to post any information about your tables, I cannot tell how you would
enforce it in a database.

I'd love to be able to help, but I can't unless you tell me what's in your
database!
--

John W. Vinson [MVP]
.

John i forgot the other fields

Table: Employee
LName
FName
Hire Date
Office Staff 30 days for eligibilty from hire date
Transport 30 days for eligibility from hire date
Manager 30 days for eligibility from hire date
Maint 30 days fro eligibilty from hire date
Clerk 90 days for eligibility from hire date

Will this help?
Thank you John

"John W. Vinson" wrote:

On Fri, 16 Apr 2010 09:32:01 -0700, dar wrote:

Yes, managers are 30 days from hire date, clerks are 90 days from hire date.


That's a business rule.

It's not a database rule.

I can see how you would enforce that in your office, but since you have chosen
not to post any information about your tables, I cannot tell how you would
enforce it in a database.

I'd love to be able to help, but I can't unless you tell me what's in your
database!
--

John W. Vinson [MVP]
.

On Fri, 23 Apr 2010 10:39:02 -0700, dar wrote:

John i forgot the other fields

Table: Employee
LName
FName
Hire Date
Office Staff 30 days for eligibilty from hire date
Transport 30 days for eligibility from hire date
Manager 30 days for eligibility from hire date
Maint 30 days fro eligibilty from hire date
Clerk 90 days for eligibility from hire date

This isn't making sense. Does each employee have a Office Staff field, a
Transport field, a Manager field??? What is contained in this field - a date?
If an employee is a clerk, why does she need a Transport field?

--

John W. Vinson [MVP]

On my last reply I forgot to put the Eligibility date goes with the info on
put on the titles. Office, transport etc. Eligibility date will be based
off the hire date.

"John W. Vinson" wrote:

On Fri, 16 Apr 2010 09:32:01 -0700, dar wrote:

Yes, managers are 30 days from hire date, clerks are 90 days from hire date.


That's a business rule.

It's not a database rule.

I can see how you would enforce that in your office, but since you have chosen
not to post any information about your tables, I cannot tell how you would
enforce it in a database.

I'd love to be able to help, but I can't unless you tell me what's in your
database!
--

John W. Vinson [MVP]
.

I have created a field labeled; HireDate30 and HireDate90 and would like to
calculate the eligibility date based off of the HireDate30 and HireDate90. I
think that would make is simpler than trying to calculate it off of the
titles, right?

Thank you

"John W. Vinson" wrote:

On Fri, 16 Apr 2010 09:32:01 -0700, dar wrote:

Yes, managers are 30 days from hire date, clerks are 90 days from hire date.


That's a business rule.

It's not a database rule.

I can see how you would enforce that in your office, but since you have chosen
not to post any information about your tables, I cannot tell how you would
enforce it in a database.

I'd love to be able to help, but I can't unless you tell me what's in your
database!
--

John W. Vinson [MVP]
.

On Fri, 23 Apr 2010 11:53:01 -0700, dar wrote:

I have created a field labeled; HireDate30 and HireDate90 and would like to
calculate the eligibility date based off of the HireDate30 and HireDate90. I
think that would make is simpler than trying to calculate it off of the
titles, right?

Again:

What is the datatype of hiredate30 and hiredate90?
Does every employee have a Hiredate30 and also a Hiredate90?
If so why?

I really think you may be misunderstanding how tables work. They're not
spreadsheets! A Table represents a particular type of Entity - real-life
person, thing or event. Each Field in the table contains the value of some
specific Attribute of that entity - the person's FirstName, their LastName,
their HireDate, their PositionID and so on. If you have several mutually
exclusive attributes (i.e. if someone has a Hiredate30 then their Hiredate90
must be blank), your table structure is wrong.

I don't understand your business model, but if you'll allow me to grope in the
dark with a possible idea... consider the following tables:

Employees
EmployeeID autonumber primary key
LName
FName
HireDate
PositionID

Positions
PositionID autonumber primary key
Position e.g. Clerk, Manager, High Muckamuck
DaysToEligibility

You could then create a query joining these two tables and calculate the
eligible date. The SQL view of the query (copy and paste it into a new query's
SQL view) would be

SELECT LName, FName, DateAdd("d", [DaysToEligibility], [HireDate]) AS
DateEligible
FROM Employees INNER JOIN Positions
ON Employees.PositionID = Positions.PositionID;

You can put criteria on the DateEligible calculated field if that's what
you're trying to do.
--

John W. Vinson [MVP]