Search results for query: *

I concur with Charles, replace table should work and if it is not, it sounds like you have an access issue. Hound ADP to get their Reportsmith help to call you back. Ask them to send a "hot" case.

Yes, I do it all of the time. Simply create a derived field with the heading name that you want and just put ' ' in the box. Save, and you're done. It'll make a blank field.

Not sure what system/database you are using, but this can definitely be done in an Enterprise environment. What I do is simply choose "none" for the effective date option, and then make the fields I want "query only". Then I'd just create derived fields looking for each month January...

If the table is not effective dated, then I believe you are out of luck.

Adding to my above post: i.e., a selection of: V_HRP_HSTEMPSTATUS.EFFDT is equal to 12/31/07

Sounds like you are running PCPW with HR Perspective, and unfortunately I don't have specific experience with the HRP tables. However, I can tell you that if it is an effective dated table, you'd simply want to include the effective date field (in Enterprise, it's called "EFFDT") in the report...

Correction to my last paragraph: But bottom line if I am to revisit this issue, I need to somehow create a report where I can bring in the inc_amt and inc_pct fields associated with the most recent actions PAY or PRO (and in some cases, XFR) but still keep ALL records (meaning every employee...

Thank you both for your help, it was great learning experience for me. As it turns out though, the report was still dropping some records. I ended up getting the report within arms length of working perfectly, but ultimately scratched the project for now. I had it showing last increase...

I get what you're saying. Anyway, thanks a ton for your help it's greatly appreciated. I just moved into this position, and the previous person was running a report with ALL historical data and then running it through a query in Access to weed out data. Needless to say, it was an...

Wow, that worked! I still have one or two duplicates, but that's because of poor data entry on our payroll side -- I can work with that easily. I don't know if it is outside the scope of what can be explained here, but I'd really like to understand why that worked, but the other method...

I verified the SQL line for line, that seems to cause the exact same problem. It excludes employees whose last action was not either "PAY" or "HIR"

I'll give it a shot when I have a few minutes and let you know how it goes. Thanks!

In my previous post, ignore the part where I need to see only "MER" or "HIR" action reason -- that is incorrect. Stick to "PAY" or "HIR" action as those encompass all of the various "Action Reasons" that I need.

Charles, Thank you for your response, however that route doesn't quite work, let me explain. I need to see the last action which was a "PAY" action type or "MER or HIR" action reason. If I effective date the table, it will show me only the people whose LAST action were one of those, but...

Hi there, I am new to this forum but it looks like a great place to network -- So thank you ahead of time for any assistance that can be offered. I am currently building a report in ADP Enterprise using Reportsmith version 3.10, and I am having an issue with history. A little background...