If statement in Query
Experts,
I've attached my db so you can better "see" what my objective is.
In the form frmBonusEarned I use 4 unbounded text controls that read from the combo box called StoreID. This form is my input form from which my calculations will be based upon.
Here's what can happen. An employee may no longer be an active employee and therefore would not be eligible for any store bonuses. In the table tblEmployee there is a Y/N field called Active. In my unbounded text controls I need to evaluate to see if the Employee is Active and if not the display some message such as "No Manager Assigned".
StoreBonus.mdb
I've attached my db so you can better "see" what my objective is.
In the form frmBonusEarned I use 4 unbounded text controls that read from the combo box called StoreID. This form is my input form from which my calculations will be based upon.
Here's what can happen. An employee may no longer be an active employee and therefore would not be eligible for any store bonuses. In the table tblEmployee there is a Y/N field called Active. In my unbounded text controls I need to evaluate to see if the Employee is Active and if not the display some message such as "No Manager Assigned".
StoreBonus.mdb
Rey Obrero (Capricorn1)
which employee are you referring to, after populating all the unbound controls ?
ASKER
A store can have 4 employees that can participate in a store bonus:
District Manager
Assistant Support Manager (if there is one)
Store Manaager
Assistant Store Manager
If any of those are not active then they ate tagged as No in the tblEmployee - Active field, and would not particiapate in any bonuses. The control would could read None in the form frmBonusEarned
District Manager
Assistant Support Manager (if there is one)
Store Manaager
Assistant Store Manager
If any of those are not active then they ate tagged as No in the tblEmployee - Active field, and would not particiapate in any bonuses. The control would could read None in the form frmBonusEarned
so, you are saying that before showing the names to the corresponding textbox,
check first if they are active or not ?
check first if they are active or not ?
Can you enter some bonus so that we can see what you are trying to achieve.
Also you db would be much easier to navigate an query if you tblDesignatedEmployee was set as:
DesignatedEmployeeID,Store
The designationID is a lookup field to a designation table which would have the name of all you positions
Also you db would be much easier to navigate an query if you tblDesignatedEmployee was set as:
DesignatedEmployeeID,Store
The designationID is a lookup field to a designation table which would have the name of all you positions
ASKER
that's correct. If they are no longer active no bonus
ASKER
sb9:
I haven't got that far on data entry - I'm sure a whole new set of problems will come up there. I'm not sure I understand the second part on the structure - if you all think my structure needs to be different I'm open to that also
I haven't got that far on data entry - I'm sure a whole new set of problems will come up there. I'm not sure I understand the second part on the structure - if you all think my structure needs to be different I'm open to that also
ASKER
sb9:
I could changed the tblDesignatedEmployee as suggested. I'd have to change the form frmDesignate Employee. Cap, what do you think?
I could changed the tblDesignatedEmployee as suggested. I'd have to change the form frmDesignate Employee. Cap, what do you think?
Just use some dummy data otherwise it will be impossible to figure out if what we are doing is really working. The table are relational and since you do not have employeeID in tblBonusEntered which is the recordsource of the subject form you would need a query to find the corresponding employeeid. If there are no data in the tables involved the query is not going to work properly.
RE: My second statement:
It is best not to "hard code" the position in the table field. The will make is easier to add more position or reduce position. Also queries will be much simpler if your are not pointing to 4 employeeid in a single record.
RE: My second statement:
It is best not to "hard code" the position in the table field. The will make is easier to add more position or reduce position. Also queries will be much simpler if your are not pointing to 4 employeeid in a single record.
ASKER
there is data already except for the dollars - I plan on first captuting the data then create the queries and reports I will need. I do understand the change in the table structure now. I would need to throw the baby out with the bath water, close this question down and resubmitt if necessary. I know capricorn has responded and I don't want him to be going in one direction and me in a total different one.
Fair comment. I have started to work on an approach that will keep the look of the current frmDesignate and work with the new structure. Just open a new related question and we will work from it there. You may proceed with the if query component of you question in the current thread.
@ Capricorn: What's your views
@ Capricorn: What's your views
ASKER
thank - capricorn, are you ok with this?
Opps, missed the comments and compact and repair to reduce file size.
Check out the new frmDesignate Employee. NB recordsource for the mainform is tblStore and each designation is actually a subform based on 4 new queries. I have also use an onclick event in the control of the subforms to add the designation.
StoreBonus-1-.mdb
Check out the new frmDesignate Employee. NB recordsource for the mainform is tblStore and each designation is actually a subform based on 4 new queries. I have also use an onclick event in the control of the subforms to add the designation.
StoreBonus-1-.mdb
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
you sure went the extra mile on this - thanks and GREAT job. I truly appreciate the Experts!