What are you having the most problem with, the fact that it must record staff holidays or the security part? or both seeing as how you are a lazy bugger and all?

Heh.

Both.

For security, I can use the logon Id and workstation id stuff from the other day - I just need to find a way to disable access to the backend with the shift key, which shouldn't be too hard.  none of my users know anything about Access, anyway.

Not quite sure how to start at the moment - I have the usual high standard of requirements - i.e. 'we need a database to record staff holidays on... can you do it in that access thingie?'  I'm sure they'll come up with all sorts of useful comments after the event!

What I'm pretty sure I want, though is some sort of authorisation procedure, so that the line manager much confirm the holiday once it's been input.  And it needs to keep a record of any changes made.  And it has to be really easy to use - and most importantly, it should not require ANY paper at all, no matter how obsessed with bits of paper the bosses are.

-- Edited by ddvmor at 09:22, 2004-12-16

I don't remember the teacher from Charlie Brown.  Did he have a holiday database?

R. Hicks has a shift key bypass demo that is pretty handy in the code archives here as for the keeping track of changes, search for audit trails and such

Audits are kinda of a pain in the butt with access because you have to code everything yourself. The simplest thing to do is just record when a record changes, not neccessarily how it changes. The how part gets complex and adds to the size of the database imensely. If you were using SQL Server or Oracle, these DBMS's capture the "how" part for you and you can do stuff with it then using triggers.

Uh oh!

So, let's say you do build this DB, and I for one am all for it, will this mean that fcukers at work will no longer be able to fubar Suey-mate's Excel application?

I'm tired of people trying to do $h*t like this in Excel!

-- Edited by NateO at 00:02, 2004-12-18