Brian,
Believe me I know this! It's my predecessor that was super naughty. We do payroll inhouse within Vantage, and we have a third pary time clock app (Qqest TimeForce). He wrote an Excel VBA app that takes a .CSV output from the time clock app, and directly inserts records to the LaborHed/LaborDtl tables, and updates the Labor_SEQ record (argggghhhhh!). We make the employee ID and Department the same in both systems, but the potential for entry error and leaving orphaned records is huge! We don't own Service Connect, and I have been trying to make a business case for it for some time now, with no support from management. The problem is when the only tool you have is a hammer, everything looks like a nail. My predecessor knew VBA and could write some simple SQL queries, so that's what he did. Personally, I don't have the *cajones* to start inserting directly into the tables within an app that I didn't personally develop. I'm fine with read only for reporting purposes, but I'm with you 100%. Maybe I can use you as a testimonial next time I confront management and try to buy Service Connect. We can't continue to do this because Brian says so...
Cheers,
Jared
Believe me I know this! It's my predecessor that was super naughty. We do payroll inhouse within Vantage, and we have a third pary time clock app (Qqest TimeForce). He wrote an Excel VBA app that takes a .CSV output from the time clock app, and directly inserts records to the LaborHed/LaborDtl tables, and updates the Labor_SEQ record (argggghhhhh!). We make the employee ID and Department the same in both systems, but the potential for entry error and leaving orphaned records is huge! We don't own Service Connect, and I have been trying to make a business case for it for some time now, with no support from management. The problem is when the only tool you have is a hammer, everything looks like a nail. My predecessor knew VBA and could write some simple SQL queries, so that's what he did. Personally, I don't have the *cajones* to start inserting directly into the tables within an app that I didn't personally develop. I'm fine with read only for reporting purposes, but I'm with you 100%. Maybe I can use you as a testimonial next time I confront management and try to buy Service Connect. We can't continue to do this because Brian says so...
Cheers,
Jared
--- In vantage@yahoogroups.com, "Brian W. Spolarich " <bspolarich@...> wrote:
>
> Messing with the UD* tables is fine, but otherwise you're playing with
> fire.
>
> -bws