Creating a Sign in Form..

[bitsbb01]

Ok i'm having a few problems, as Access only allows 255 collumns and not sure how else to do this.. so hopefully someone else has already had this problem or even knows a way round it..

I've been tasked with building a sign-in form for staff to use daily..
with multiple fields..

Date. Username. Sign-in (Morning). Sign-out (Lunch). Sign-in (Afternoon). Sign-out (End Of Day)

problem is theres 60+ staff and way i thought of doing it, was to allocate new record per day, on the form, each staff would goto there name, and put in time in the relevant box.. however to have this many colloumns to cover for it all, goes over 255 collumns.

I've created a similar one before for our Kiosk machines, however theres only 20 Kiosk machines

once the form & table is created, i'll need to make it so Managers can log into it and see the whole form and see who's here and who isnt..

Any Ideas how to do this, or even if its possible??

 

[KenshiroUK]

Would this help? http://www.youtube.com/watch?v=TB3Qp1pdNOY

 

[plog]

Tables shouldn't expand to hold data horizontally, they should expand vertically. The answer usually isn't more columns, its more rows. I can't envision how you will have 255 columns, but I do know you're going about it incorrectly if that's a solution you are thinking about implementing.

Based on your description a table that looks like this will do what you need:

Signings
UserID, SignTime, Direction
13, 6/13/2013 8:00 am, In
16, 6/13/2013 8:01 am, In
13, 6/13/2013 11:58 am, Out

Or at worst case this:

Signings
UserID, InTime, OutTime
13, 6/13/2013 8:00 am, 6/13/2013 11:58 am
16, 6/13/2013 8:02 am, 6/13/2013 12:11 pm

 

[bitsbb01]

ok plog the way i currently have it, and so Reports can be created easily..

ID, Date, User1, User1 Sign-in, User1 Lunch, User1 Sign-in PM, User1 EOD, User2, User2 Sign-in, User2 Lunch, User2 Sign-in PM, User2 EOD, And So on..
so once you got 60+ you easily hit 255 Columns..

so basicly each record is a new day..

otherwise we have to include searchs for it to search the correct ID etc for each user, this way, at end of each day, we just hit new day (new record).


Hmmm just been looking at the MS Template, and might be able to get that to work.. hopefully.. lol

 

[plog]

I'm not doubting that you'll hit 255 columns doing it the way your doing it. It's that you shouldn't be doing it that way, at least not with the tool you've chosen.

My method is the correct one for the tool (Access) you have chosen. If you want to use a spreadsheet for this, then use a spreadsheet for this and not a database--nothing wrong with that. But don't choose the right tool and expect to use it the wrong way and get where you want to go without problems.