User Profile

Collapse

Profile Sidebar

Collapse
Dani
Dani
Last Activity: Mar 25 '14, 09:31 PM
Joined: Mar 6 '12
Location:
  •  
  • Time
  • Show
  • Source
Clear All
new posts

  • Dani
    replied to Need help with table normalization please
    I did think of a crosstab query after I posted. I think you're right that once I isolate the SV, Employee and date of evaluation, I'll get the appropriate record.
    thanks so much for your input.
    Dani
    See more | Go to post

    Leave a comment:


  • Dani
    started a topic Need help with table normalization please

    Need help with table normalization please

    Hi,
    I'm developing and HR database with Access 2010. I've hit a snag with designing a Performance Evaluation table.

    I have various lookup tables for:

    EmployeeID
    SupervisorID
    PerformanceRati ngID (eg. Average, Outstanding)
    EvaluationAreaI D (eg. Attendance, Housekeeping)

    Each employee will have multiple evaluations from different supervisors. Each evaluation will contain contain...
    See more | Go to post

  • Dani
    started a topic Null as falsepart of IIf Statement

    Null as falsepart of IIf Statement

    Hi,

    I'm looking for some guidance on how to approach a problem. We are continuously pulling recurring work order tasks from one database into a new one that I've built in Access (one with more ability to track man hours and other info). Most of the fields map nicely.

    The trades field in the original is rather polluted. It was called AssignedTo and instead of simply having Electrician and Mechanical as choices, multi-users...
    See more | Go to post
    Last edited by zmbd; Feb 22 '13, 07:15 AM. Reason: [Z{Please use the <CODE/> formatting button to format your posted code and SQL}]

  • Dani
    replied to Tricky Date Criteria
    As said, I'm pretty new to Access so this causes some serious growing pains for me, but it's good to learn and stretch. I really like what Access can do and enjoy trying to solve these little puzzles myself (when they're not above my skill level.)

    I've been sidetracked today with a production report form that is sketched out in Word, converted to PDF and combo boxes added. All I can think (screaming in my head) is that this would...
    See more | Go to post

    Leave a comment:


  • Dani
    replied to Tricky Date Criteria
    You'll send me a bill? lol

    I so appreciate this, NeoPa, thank you. Yes, you are correct that (in theory) no employee would have two gaps in their record. Unless I am extremely careless in loading the data when we go live ;o)

    I will try this with my dummy data. Thanks again,
    d
    See more | Go to post

    Leave a comment:


  • Dani
    replied to Tricky Date Criteria
    Good question and one I haven't completely wrestled to the ground.

    I think a query to pull the employees with incidents 2 yrs or older and a query to pull all incidents. Then maybe a Find Unmatched? That might be messy, but because I don't know much for code, I tend to take the long walk past Grandma's house to get to where I want to be.

    As for triggering it, I've been trying to set up a form so the Main form is the...
    See more | Go to post

    Leave a comment:


  • Dani
    replied to Tricky Date Criteria
    I missed this comment as I had not refreshed my screen:

    "Explaining that a little more clearly (As Rabbit says it's not about deleting data), does data prior to a two year long gap get included if a subsequent infringement/issue is logged?"

    No. In this situation they would start again at first Verbal Warning.

    From a privacy standpoint, it seems better practice to purge the Employee's record...
    See more | Go to post

    Leave a comment:


  • Dani
    replied to Tricky Date Criteria
    It's a very valid concern about the process, so I thank you for bringing it to my attention. I've now discussed it with the HR Mgr and he has instructed me to purge an employee's record once they have passed the two year mark.

    This simplifies the query writing since only employees with records will be in the table.

    Thanks for your help Neopa & Rabbit,
    cheers,
    d
    See more | Go to post

    Leave a comment:


  • Dani
    replied to Tricky Date Criteria
    Excellent comment and not something I had considered doing. My first instinct is to preserve the information, but purging would be more in line with genuinely wiping their record.

    The database is still in development stages so this is an excellent discussion for me to have with our HR Manager.

    Thank you for this.
    Dani
    See more | Go to post

    Leave a comment:


  • Dani
    replied to Tricky Date Criteria
    Obviously I was still a bit muddy, but thank you :)

    To clarify, if Employee has an incident in 2009 and nothing else until today, his incident in 09 would not be counted.

    If Employee has an incident in 2009 and then in '10 and '11 and today, all previous incidents would be counted.

    They are then issued a statement like, "As this is your fourth incident, you are now under suspension" Or "As...
    See more | Go to post

    Leave a comment:


  • Dani
    started a topic Tricky Date Criteria

    Tricky Date Criteria

    Hi,

    I'm working on an HR database and I want to write a query that counts discipline records for the employees.

    Here's the tricky part. Incidents are 'current' for two years. If an employee goes 2 yrs without an incident, their record is wiped clean. If they have an incident within the 2 yr mark, all previous records are counted no matter how far they go back.

    Here are my fields:
    DisciplineID...
    See more | Go to post

  • Dani
    replied to Removing a lookup field from a table
    I think I've got it figured... Open the Table in Design View, click on Look Up tab and change Combo to Text. Delete data in the tables, then create the look up Tables, relate and redesign forms to enter new data. Seems to be working.
    See more | Go to post

    Leave a comment:


  • Dani
    started a topic Removing a lookup field from a table

    Removing a lookup field from a table

    I'm a newbie who went ahead and designed my tables with lookup fields because I didn't know any better until I couldn't get the results I wanted in my report. I am now in on the secret--they ARE evil.

    The good news: this DB hasn't been published, I'm very much open to going back and removing/converting those lookup fields, but I'm not sure the best way to attack it?

    I'm working in Access 2010. This is essentially...
    See more | Go to post
No activity results to display
Show More
Working...